PageAudit exposes a single tool 'audit' with minimal definition quality. The tool name lacks a clear action verb (should be 'audit_page' or 'run_page_audit'). Description is extremely brief (11 chars: 'Audit a page'), below the 20-char minimum for actionable guidance. Input schema is present but sparse: only 'url' parameter with a basic string type and minimal description. No output schema is documented, LLMs cannot predict what fields the response contains or how to chain results. No error handling guidance, no pagination support, no parameter constraints (e.g., valid URL format).

• Expand tool description to 50-150 chars: 'Audit a web page for performance, accessibility, and SEO issues. Returns a structured report with scores and recommendations. Accepts HTTP/HTTPS URLs only.'
• Document output schema explicitly: describe all top-level keys in the report object (e.g., 'scores', 'issues', 'recommendations'), their types, and what each represents.
• Rename tool from 'audit' to 'audit_page' to follow verb_noun convention and improve LLM intent clarity.
• Add URL parameter constraints: specify format (must start with http:// or https://), max length (e.g., 2048 chars), and behavior on invalid/unreachable URLs.
• Add error handling guidance: document timeout behavior (e.g., 60s limit), what happens if URL is unreachable, and whether retries are safe (idempotent).