Google Search Console MCP

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

No annotations provided, so description carries full burden. It discloses important behavioral context: domain properties cover all subdomains, the 500-row hard limit, and pagination limitations. Missing explicit mention of rate limits, authentication requirements, or error states (e.g., invalid page URLs).

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?

Uses standard Args docstring format with high information density. Every line provides actionable guidance (examples, value ranges, alternative tools). Slightly verbose due to inline examples, but no wasted words.

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?

Despite thorough parameter documentation, the description lacks return value specification. With no output schema provided, the agent cannot determine what metrics are returned (clicks, impressions, CTR, position) without invoking the tool. This gap impedes tool selection confidence.

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 all 4 parameters extensively. site_url includes format examples and domain property behavior; row_limit includes usage heuristics; days and page_url include clear semantics. Adds significant value beyond the schema titles.

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 opening sentence provides a specific verb ('Get'), resource ('search analytics data'), granularity ('broken down by query'), and scope ('for a specific page'). It clearly differentiates from sibling tools like get_advanced_search_analytics by explicitly naming it as the alternative for bulk exports.

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?

Explicitly states when to use the alternative tool ('For bulk exports beyond 500 rows, use get_advanced_search_analytics'). Provides detailed heuristics for the row_limit parameter ('Use 5-20 for quick overviews...') and specifies the prerequisite workflow for site_url ('from list_properties').

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