Playwright MCP has 15 tool categories but lacks visible input schemas and parameter descriptions in the provided source. Tool definitions are inferred from file structure (src/tools/*.ts) rather than explicitly visible in the code sample. The tool.ts file shows a ToolSchema type definition with name, title, description, and inputSchema fields, but actual schema implementations are not shown. Descriptions are present at the category level ('Common browser automation tools') but are generic and under 50 characters. No parameter-level documentation is visible. The server uses STDIO transport, which is a hard cap at 50. Critical gaps: no visible JSON Schema definitions, no parameter descriptions, no error handling guidance, no output schema documentation.

• Extract actual tool definitions from src/tools/*.ts files and document each tool's input schema as JSON Schema with type, properties, required, and descriptions for every parameter.
• Expand tool descriptions from generic labels to 50-200 character LLM-optimized text. Example: 'navigate' → 'Navigate to a URL and wait for page load. Returns page title and metadata. Use before taking actions on a page.'
• Add parameter-level descriptions for all inputs. For each parameter, state: what it controls, valid values/ranges, format (e.g., 'URL must be absolute HTTP/HTTPS'), and dependencies on other parameters.
• Implement error handling with recovery guidance. Categorize errors as retryable (network timeout → retry with backoff), user-fixable (invalid selector → suggest alternatives), or fatal (browser crashed → restart). Return actionable messages, not stack traces.
• Document output schemas per tool. Specify which fields are returned, their types, and which IDs/references can be passed to downstream tools. Example: 'screenshot returns {url, width, height, timestamp}; pass url to vision tools.'