Google Search Console MCP

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It adds valuable GSC-specific context that domain properties cover all subdomains and mentions the default day range behavior. However, it omits what data the overview returns (metrics, dimensions, aggregation level) and doesn't disclose safety characteristics or error behaviors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The docstring format with a one-line summary followed by Args section is efficient and front-loaded. The content is appropriately sized given the need to compensate for zero schema coverage, though the domain property explanation is slightly verbose (but justified by the complexity of GSC property types).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter tool with simple types, the description adequately covers inputs. However, given the absence of an output schema, the description should explain what the 'performance overview' contains (e.g., clicks, impressions, CTR) to be complete. As written, users must invoke the tool to discover its return structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by documenting both parameters in the Args section. It provides concrete examples for site_url formats ('https://example.com/' vs 'sc-domain:example.com') and explains the domain property scoping behavior, adding significant semantic value beyond the raw schema types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('Get') and resource ('performance overview'), but fails to differentiate from sibling analytics tools like get_search_analytics or get_advanced_search_analytics. In a crowded toolset with multiple analytics options, the description doesn't clarify what makes this an 'overview' versus detailed analytics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the Args section provides useful guidance on site_url formatting (referencing list_properties and explaining domain properties), there is no explicit guidance on when to use this tool versus alternatives like get_search_analytics or compare_search_periods. The 'when-not-to-use' guidance is absent despite clear sibling overlap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.