This server has 18 tools with basic definitions but significant quality gaps. Tool names follow verb_noun convention (good), but descriptions are formulaic and lack LLM-optimized depth. Parameter descriptions are mostly absent or generic. Input schemas are present with type definitions but lack validation constraints (enums, ranges, patterns). No output schemas are documented. Error handling is minimal. The server lacks parameter descriptions that would guide LLM reasoning. Example: 'element_click' has no description for the 'coordinates' parameter or how it interacts with 'selector'. 'javascript_execute' accepts arbitrary script with no validation or safety guidance. Common pattern violations: no parameter descriptions for 50%+ of params, no documented output schemas, generic descriptions that don't explain when/why to use each tool, no error recovery guidance.

• Add parameter descriptions for ALL parameters. For each tool, document: what each parameter controls, accepted format/range, and how it interacts with other params. Example: 'tabId (string, optional): Browser session identifier. If omitted, uses the most recently active session.'
• Document output schemas for every tool. Specify returned fields, types, and structure. Example for session_list: returns { sessions: Array<{ tabId: string, url: string, status: 'active'|'closed', createdAt: string }> }
• Add error recovery guidance to descriptions. Example for page_navigate: 'Returns error if URL is malformed or unreachable. Try with a simpler URL (e.g., https://example.com) or use session_list to verify the tab exists.'
• Clarify mutual exclusivity for selector vs coordinates in element_click and element_drag. State: 'Either selector or coordinates must be provided, but not both. selector takes precedence if both are given.'
• Add validation constraints to javascript_execute: 'Script must be valid JavaScript. Avoid infinite loops and long-running code (timeout: 30s). Requests for dangerous operations (file access, process spawn) will be rejected.'
• Document tabId default behavior consistently across all tools: 'If tabId is omitted, the tool uses activeTabId (the most recently created or interacted-with session). Call session_list to see all available tabs.'
• Add dependency hints to descriptions. Example for input_type: 'Requires the target element to exist and be visible. Call element_wait(selector) first if the field might not be ready.'