Server has 4 tools with complete input schemas and descriptions. Tool names follow verb_noun convention (search_analytics_query, list_sitemaps, list_sites, url_inspection). Descriptions are present and substantive (100-200 chars typical). However, parameter descriptions lack detail on constraints, valid ranges, and error conditions. Output schemas are not formally documented, only inferred from docstrings. No error handling guidance or recovery paths. Missing tool annotations (readOnlyHint, idempotentHint). All tools are read-only but this is not declared in metadata.

• Add formal JSON Schema output definitions to each tool. Document return type as object with typed fields (e.g., clicks: integer, impressions: integer, ctr: number, position: number for search_analytics_query).
• Expand parameter descriptions with constraint details: 'row_limit: integer, 1 - 25000, default 1000' and 'dimensions: array of enum [query, page, device, country, date, searchAppearance]'.
• Add error handling: wrap API calls in try-except, catch auth errors, rate limits, and invalid inputs, return actionable messages like 'Invalid site_url format. Use https://example.com/ or sc-domain:example.com'.
• Declare tool annotations in FastMCP registration: use readOnlyHint=True and idempotentHint=True for all 4 tools to signal safety to LLM.
• Implement pagination for list_sitemaps and list_sites: add limit and offset parameters, return total_count and next_offset in response.