@polinasok the DAP spec does not know what exact UI a DAP client uses. So the description of the "text" property is accurate.
If you do not see the "text" showing up anywhere in VS Code, then it makes sense to create an issue against VS Code.
BTW, please note that DAP has an ExceptionInfo request to provide additional information about an exception.

@isidorn where does VS Code show the "text" property? Is it on hover?

It is shown on the hover of the "PAUSED ON EXCEPTION" element.
Code pointer

FYI when debugging javascript, I couldn't hover of the PAUSED ON EXCEPTION because the 'profile' button always appears and interferes. But I do see some exception details in the code section. Not sure though if that's from the ExceptionInfo response or the text property.

@hyangah the exception details are coming from the ExceptionInfo request.

@isidorn are you aware of the "profile"button interaction?

@weinand @hyangah I missed the "profile" button interaction.
A workaround would be to show it as hover over the whole session element. Currently on hover it just says "Session" which is not that useful. What do you think?

I've moved the issue to VS Code because the discussion has revealed a VS Code implementation issue.

Ok. I will make the change as I suggested above, hover over the whole Session element will show the text if adapter provided it.
@doudou you can try it out with vscode insiders starting from Friday.

I am able to get the hover when raising an exception in Python. The log shows:

                 "type": "event", 
                 "event": "stopped", 
                 "body": {
                     "preserveFocusHint": false, 
                     "description": "('spam', 'eggs')", 
                     "text": "Exception", 
                     "allThreadsStopped": true, 
                     "reason": "exception", 
                     "threadId": 1
                 }

Setting the exact same stopped event fields in my new Go adapter:

{"seq":0,"type":"event","event":"stopped","body":{"reason":"exception","description":"Some description","threadId":1,"text":"Exception","allThreadsStopped":true}}

I get very different UI behavior. Description is ignored.

When I hover, "paused on exception" turns into a control panel

So there seems to be more to impacting what the UI shows, then just setting the fields in the Stopped Event. Perhaps, having or not having support for ExceptionInfo plays into this as well?

@isidorn any additional insights?

Insiders with my fix is not yet released. Please try this out with VS Code insiders from tomorrow or next week.
As for the description of the exception, that seems like a different but similar issue, can you please file a new issue for this. Thanks