Server provides 6 tools with complete input schemas and descriptions. Naming follows verb_noun convention (cwv_audit_site, cwv_optimize_html, etc.). Descriptions are present and substantive (80-150 chars), exceeding the 10-char minimum. However, parameter descriptions lack depth, most are 1-2 sentences without format constraints, ranges, or validation guidance. Output schemas are not documented in the visible code; audit result structure is inferred from dataclass definitions. Error handling is minimal, no recovery guidance or actionable error messages visible. Tool composition is sound (each does one thing), but parameter validation rules are not explicit in descriptions.

• Convert 'device' parameter to an explicit enum in schema: {"type": "string", "enum": ["mobile", "desktop"], "description": "Device type for audit..."}. Update description to reference the enum.
• Document output schema for cwv_audit_site in tool description: 'Returns AuditResult with fields: score (0-100), grade (A+-F), vitals (dict of metric objects), diagnostics (list of findings), stats (dict), summary (string), timestamp (ISO 8601).'
• Add validation constraints to parameter descriptions. E.g., 'max_age_seconds: Cache duration in seconds (1-31536000, default 31536000 for 1 year).' Include min/max for all numeric params.
• Define schema for cwv_optimize_html 'options' object. Document valid keys: add_dimensions (bool), add_preconnects (bool), defer_scripts (bool), etc. Provide example: {"add_dimensions": true, "defer_scripts": true}.
• Add error handling guidance to tool descriptions. E.g., 'If URL is unreachable, try a file:// path or raw HTML content. If platform is unsupported, check cwv_generate_cache_config description for valid platforms.'

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

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