Single tool 'browser_install' has a description but lacks a visible input schema in the source code. The tool is referenced in auth-proxy.ts for role-based access control, but no explicit JSON Schema definition, parameter types, or output schema are documented. The description is minimal (67 chars) and does not explain what the tool returns, when to use it, or what parameters it accepts. No parameter documentation visible. Tool composition is unclear, it appears to be a write operation but lacks error handling guidance or recovery instructions.

• Define explicit JSON Schema for browser_install with all input parameters (types, required fields, descriptions, constraints). Example: { type: 'object', properties: { os: { type: 'string', enum: ['linux', 'macos', 'windows'], description: 'Target OS for browser installation' } }, required: ['os'] }
• Expand tool description to 100-200 chars explaining: (1) What it does (installs browser dependencies), (2) When to use it (before running Playwright tests), (3) What it returns (success/failure status, installed version), (4) Prerequisites (requires Tenant Admin role).
• Document each parameter with type, format, constraints, and examples. E.g., 'os (string, required): Target operating system, one of: linux, macos, windows. Determines which browser binaries are downloaded.'
• Add error handling guidance: 'If installation fails due to disk space, return error code INSUFFICIENT_DISK with available space. If network fails, return NETWORK_ERROR with retry guidance. If user lacks Tenant Admin role, return PERMISSION_DENIED.'
• Document output schema: 'Returns { success: boolean, installed_version: string, message: string }. On success, installed_version is the Playwright version installed (e.g., '1.40.0'). On failure, message explains the cause and next steps.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry