I was looking at the new support for conditional exceptions and I have two suggestions:

1. Handling errors - The protocol doesn't specify what an adapter should do if the user input an invalid condition. I feel like the right answer is that an adapter can just fail the SetExceptionBreakpointsRequest. But I felt like maybe this should be called out?
2. Providing help text - for the C#/C++ extension, I don't know that it will be super obvious to folks what syntax they should use for conditions. It would be helpful if ExceptionBreakpointsFilter had an additional optional description field that would be displayed in a datatip similar to the experience of edited launch.json in VS Code. This would allow a debug adapter to provide examples and link to complete documentation.