18 tools with consistent verb_noun naming (browser_list, browser_get, browser_click). All tools have descriptions (10-80 chars, mostly adequate). Input schemas present for all tools with typed parameters. However, descriptions are terse (avg ~40 chars vs baseline 194 chars), lack WHEN/WHY context, and omit actionable error guidance. Parameter descriptions are minimal (avg ~30 chars vs baseline 72 chars). No output schemas documented. Missing idempotency hints for write operations. No pagination guidance despite tools accepting optional limits. Error handling not visible in tool definitions.

• Expand tool descriptions to 100-200 chars. Include WHAT (action), WHEN (use case vs similar tools), and WHAT IT RETURNS (output structure). E.g., 'Get the HTML DOM tree of the current page. Use this to inspect page structure; use browser_get_text for text content only. Returns {html: string, frameId: int, documentId: string}.'
• Add 50-100 char descriptions to every parameter. Explain the type, valid range, and what happens if omitted. E.g., 'Tab ID (integer, required): The numeric ID of the browser tab. Obtain from browser_get_tabs(). If omitted, uses the selected tab.'
• Document output schemas for all tools. Use JSON Schema format in tool metadata or a separate schema registry. E.g., browser_get_tabs returns {tabs: [{id: int, url: string, title: string, active: bool}], total: int}.
• Add idempotency and retry guidance to write operations. E.g., 'browser_click is idempotent if the element state does not change. Safe to retry on timeout. Not safe to retry if the click triggers navigation or state mutation.'
• Clarify default behavior for optional parameters. E.g., 'If browserId is omitted, uses the browser selected via browser_select(). If no browser is selected, returns an error with available browser IDs.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry