36 tools with highly inconsistent quality. Most lack input schemas entirely (inferred from file structure, not visible in source). Descriptions range from adequate (seo_crawl_site: 'Crawl a website...') to vague (seo_audit_issues, seo_page_inspect: no descriptions shown). Only 3 tools have visible input schemas with type/description pairs. No output schemas documented. No error handling guidance. Tool names follow verb_noun pattern (good), but parameter documentation is sparse. Composition is reasonable (tools chain logically), but schema completeness is critical blocker.

• Add complete input schemas to all 33 undocumented tools. Each schema must include parameter name, type (string|number|boolean|object|array), description (50-150 chars), and constraints (enum, min/max, pattern). Use JSON Schema format matching seo_crawl_site example.
• Write descriptions for all 23 tools lacking them. Format: 'Verb + what it does + when to use it + prerequisites.' Example: 'Analyze crawl results for technical SEO issues. Call after seo_crawl_site completes. Returns issues ranked by impact.' Target 80-150 characters.
• Document output schemas for all tools. Specify return type (object|array), key fields, field types, and pagination (if applicable). Example: '{summary: string, data: {issues: [{id, title, severity, fix_cost}]}, actions: [...], meta: {cost, next_calls}}'.
• Add error handling guidance to tools calling external APIs. Include: error type (PROVIDER_NOT_CONFIGURED, RATE_LIMIT, NETWORK_ERROR), recovery hint (e.g., 'Set AHREFS_API_KEY env var or use free alternative seo_crawl_site'), and retry eligibility. Follow pattern:recovery-guide.
• Add tool annotations to all tools. Mark seo_crawl_site, seo_keyword_ideas, seo_gsc_performance as readOnlyHint=true. Mark seo_project_set, seo_cache_clear as destructiveHint=true. Mark idempotent tools (e.g., seo_capabilities) as idempotentHint=true per MCP spec 2026-07-28.