[kashishhora]

Summary

The WebMCP spec has four tool annotations, but ToolAnnotations only had readOnlyHint and untrustedContentHint. Putting consequentialHint: true in a useMcpTool config failed to compile (TS2353), even though the polyfill already forwards annotations as-is. Google's new webmcp-types package and their test extension both use consequentialHint. The extension always asks the user before running a tool that sets it.

• Added consequentialHint and debugging to ToolAnnotations
• Type test for the new fields, and runtime checks that they reach registerTool and come back from getTools()
• README, docs/api.md and the add-tool skill now list all four

No runtime change.

Test Plan

• pnpm build && pnpm typecheck && pnpm lint && pnpm test (310 tests)