Chrome-mcp has 10 tools with basic naming (verb_noun pattern) and descriptions present, but significant quality gaps. All tools lack documented output schemas, critical for LLM planning. Parameter descriptions are minimal (1-2 sentences). No error handling guidance, no recovery patterns, no pagination support. Security features (stealth mode, injection defense) are implemented but not surfaced in tool descriptions. Tool descriptions average ~80 chars, below the 194-char baseline for A+ tools. Schemas are present but sparse: most parameters lack type constraints (e.g., chrome_evaluate's 'expression' is a bare string with no format guidance). No idempotency markers, no confirmation patterns for destructive ops (chrome_close, chrome_click). The server implements sophisticated anti-injection logic but does not document it in tool descriptions, leaving LLMs unaware of constraints.

• Document output schemas for all tools. Example: chrome_snapshot should return {dom_tree: string, interactive_elements: [{selector: string, text: string, type: string}], text_content: string}. This enables LLMs to chain calls and extract data.
• Expand parameter descriptions to 50-100 chars with format guidance. For chrome_evaluate: 'JavaScript expression to evaluate (read-only on LinkedIn; no DOM mutations, network calls, or escape sequences allowed).' For chrome_type: 'Text to type into the focused element (max 10000 chars; delay in ms between keystrokes, default 0).'
• Add error handling guidance to each tool description. Example: 'If selector not found, returns error with available selectors. Retry with corrected selector or call chrome_snapshot to inspect page structure.'
• Implement confirmation pattern for destructive ops. Add optional 'confirm' boolean param to chrome_close and chrome_click. If false (default), return {status: 'pending_confirmation', action: 'close_browser', message: 'Confirm to close browser'}. Require explicit confirm=true to proceed.
• Surface stealth-mode constraints in tool descriptions. Add to chrome_evaluate: 'On LinkedIn domains, this tool is read-only, write expressions are rejected. Use chrome_navigate or chrome_click for interactions.' Add to chrome_navigate: 'LinkedIn domains always use stealth mode regardless of chrome_set_mode setting.'