mcp-browse has 5 tools with basic schemas and descriptions, but significant gaps prevent production use. All tools have descriptions (10-30 chars, below the 50-200 char baseline for LLM optimization), and input schemas are present but lack depth. Parameter descriptions are minimal or missing context about constraints, formats, and dependencies. No output schemas documented. Error handling is absent, no recovery guidance, no categorization of retryable vs fatal errors. The 'Input' tool's selector parameter uses an object with conditional properties (element_id OR css_selector) but does not document this mutual exclusivity. 'ExecuteScript' accepts arbitrary JavaScript with no safety guardrails or sandboxing hints. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (Click, Input, ExecuteScript are WRITE; Navigate, Download are READ_ONLY). Composition is reasonable, each tool has one responsibility, but chaining is not documented (e.g., does Navigate return a page ID for subsequent Click calls?).

• Expand all tool descriptions to 50-200 characters. Include WHAT the tool does, WHEN to use it (vs similar tools), and what it returns. Example: 'Navigate to a URL and load the page. Returns page title, content, and available interactive elements. Call this first to discover clickable elements for subsequent Click calls.'
• Document output schemas for all tools. Specify fields returned (e.g., page_title, page_content, elements[], error_message) with types and descriptions. This enables LLMs to chain tools correctly.
• Add parameter descriptions with constraints. Example for Click selector: 'Object with exactly one of: element_id (HTML id attribute) or css_selector (CSS selector string). Mutually exclusive, pass only one.'
• Implement error categorization and recovery guidance. Return structured errors with code, message, and next_action. Example: {code: 'ELEMENT_NOT_FOUND', message: 'CSS selector .submit-btn not found', next_action: 'Try a different selector or call Navigate() to refresh the page.'}
• Add tool annotations to the schema. Mark Click, Input, ExecuteScript with destructiveHint=true. Mark Navigate, Download with readOnlyHint=true. Declare idempotency where applicable (Navigate is idempotent; Click may not be).