ChromeBridge has 27 tools with minimal schema documentation. Most tools lack visible input parameter schemas in the source code, only 2 tools (navigate, open_tab) show explicit parameter definitions. Descriptions are present but generic (10-50 chars), falling well below the 194-char baseline for production tools. No output schemas are documented. Tool names follow verb_noun convention (good), but parameter descriptions are absent for most tools. Error handling exists but lacks recovery guidance. The tool-dispatcher.cjs shows tool registration but no formal schema definitions for 25 of 27 tools.

• Add formal JSON Schema input definitions for all 25 tools lacking schemas. At minimum, define parameter types (string, number, array), required fields, and constraints (enums, min/max, patterns). Example: click should declare selector (string, required), tab_id (string, optional), timeout_ms (number, 1-60000).
• Expand all tool descriptions to 100-250 characters. Include WHAT the tool does, WHEN to use it (vs similar tools), and any prerequisites. Example: 'Click on an element matching a CSS selector. Use after find() to locate the element. Returns success status and any error details. Fails if element is not clickable or tab is not active.'
• Document output schemas for all tools. Specify returned fields, types, and structure. Example: list_tabs returns [{tab_id: string, title: string, url: string, active: boolean}]. This enables LLMs to chain tools and extract required IDs.
• Add parameter descriptions to all tools. For each parameter, state its type, valid values/ranges, and purpose. Example: selector (string, CSS selector or XPath), tab_id (string, from list_tabs), timeout_ms (number, 1-60000, default 15000).
• Enhance error messages with recovery guidance. Instead of 'UNSUPPORTED_OPERATION', return 'Tool not supported. Available tools: [list]. Did you mean: [suggestion]?' This enables LLMs to self-correct without extra discovery calls.