Server exposes 20 tools with consistent naming (verb_noun pattern) and reasonable descriptions. However, critical gaps exist: parameter descriptions are sparse or missing entirely (e.g., browser_tabs 'action' param lacks detail on what each action does), output schemas are undocumented, and error handling provides no recovery guidance. Most tools lack information about what fields they return, forcing LLMs to guess. Proxy and profile management tools are well-structured, but browser interaction tools (click, fill, evaluate) have minimal parameter documentation. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels.

• Document output schema for every tool. Example: profile_list should return {profiles: [{name, description, status, mode}], total: int}. Include this in tool description or as a separate schema field.
• Add detailed parameter descriptions. For browser_tabs, explain: action='list' returns all tabs; action='create' opens new tab at url; action='close' closes tab_id. For browser_evaluate, specify 'JavaScript code executed in browser context; returns result of last expression.'
• Implement tool annotations in server.call_tool(). Add readOnlyHint=true to profile_list, browser_health, proxy_list, proxy_get, browser_take_screenshot, browser_wait_for_selector. Add destructiveHint=true to profile_delete, proxy_delete. Add idempotentHint=true to profile_get, proxy_get.
• Enhance error messages with recovery guidance. When profile not found, return: 'Profile "xyz" not found. Available profiles: [list]. Call profile_list() to see all profiles.' When proxy not found, suggest proxy_list().
• Add confirmation pattern for destructive tools. Introduce profile_delete_confirm(name, confirmation_token) where initial call returns token. Or add dry_run parameter to preview impact before deletion.

Inferred effective spec: 2026-07-28+.

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