Server has 5 tools with complete schemas and descriptions. Naming follows verb_noun convention (gsc_list_*, gsc_search_*, gsc_inspect_*). Descriptions are present and adequate (50-150 chars), explaining WHAT each tool does. However, parameter descriptions lack actionable constraints (e.g., date format, dimension limits, filter syntax). Error handling is basic, sanitizeToolError() wraps exceptions but doesn't guide recovery. No output schema documentation visible. gsc_search_analytics has 9 parameters but lacks dependency hints (e.g., 'dimensions and filters must align'). Overall: functional but missing LLM-optimization details that would push toward 70+.

• Document output schemas for all tools. E.g., 'gsc_list_sites returns {sites: [{siteUrl: string, permissionLevel: string}], totalCount: number}'. This enables LLMs to extract and chain results.
• Add parameter constraints to gsc_search_analytics: specify which dimension combinations are valid, which filters apply to which dimensions, and how aggregation_type constrains dimensions. Use enum or pattern fields in schema.
• Enhance error messages with recovery hints. E.g., 'Authentication failed: ensure GOOGLE_APPLICATION_CREDENTIALS is set and points to a service account with Search Console read access.'
• Add dependency documentation to gsc_search_analytics description: 'Note: aggregation_type=byPage requires page dimension; data_state=all may return incomplete data for recent dates.'
• Replace example values in parameter descriptions with formal constraints. E.g., instead of 'e.g. https://.../', use description: 'GSC property URL: https://example.com/ (https scheme) or sc-domain:example.com (domain property)' with a pattern field.

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

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained