13 tools with consistent naming (verb_noun pattern) and descriptions present. However, descriptions are brief (avg ~80 chars, below 194-char baseline) and lack context on WHEN to use each tool or dependencies. Input schemas are present with type declarations, but parameter descriptions are minimal (avg ~40 chars vs 72-char baseline). No output schemas documented. Error handling and recovery guidance absent. Missing tool annotations (readOnlyHint/destructiveHint) despite clear risk levels in metadata. Composition is sound, tools are single-purpose and chainable via site_url references.

• Add output schemas to all tools. Document the structure of returned objects (e.g., search_analytics returns {query, clicks, impressions, ctr, position, ...}). This enables LLMs to extract and chain data correctly.
• Expand tool descriptions to 100-200 chars. Include WHEN to use the tool, what it returns, and any prerequisites. E.g., 'Get detailed GSC metrics for a site: crawl stats, mobile usability, Core Web Vitals. Call list_sites first if you need to discover available sites.'
• Add per-parameter validation rules and error messages. E.g., 'start_date: ISO 8601 format (YYYY-MM-DD). Must be ≤90 days in the past. If invalid, returns 400 with message: Invalid date format, expected YYYY-MM-DD.'
• Implement confirmation/dry-run for destructive tools. Add a 'confirm' boolean parameter to delete_site and delete_sitemap, or return a confirmation token that must be passed in a follow-up call. Prevents accidental deletions.
• Add tool annotations in FastMCP. Use @mcp.tool(annotations={'readOnlyHint': True}) for read-only tools and @mcp.tool(annotations={'destructiveHint': True}) for delete operations. This enables clients to warn users before execution.

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

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