Under the hood
OAuth failure messages from tool-triggered MCP connections now include richer context
What
When an OAuth authentication flow fails after being started by a tool call (for example, connecting to an MCP server), the error that gets logged and shown is now wrapped with additional context via a new helper before being reported, instead of showing the raw error text.
Why
This should make failures during tool-triggered OAuth connections easier to diagnose, since the reported error carries more context about what triggered it.