Search analytics query

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds mentioning 'pagination' and 'data freshness controls,' but these are already implied by parameters (row_limit, start_row, data_state). No additional behavioral insights beyond annotations.

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?

Single sentence of 14 words, front-loading the purpose and key features. No redundancy, but may be too terse given the tool's complexity. Could benefit from slightly more structure.

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?

No output schema, so description should indicate what the response contains (e.g., rows of data). It fails to explain return values, use cases, or data limitations. Given the tool's 10 parameters and 3 required fields, the description is too sparse.

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?

Schema description coverage is only 10% (only site_url has a description). While the description vaguely mentions dimensions, filters, pagination, and data freshness, it does not explain individual parameters or their meanings. For a tool with 10 parameters, this is insufficient to help an agent select correct values.

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 clearly states the tool queries clicks, impressions, CTR, and position from Search Console, listing key features. It distinguishes from siblings by focusing on search analytics querying, but could be more explicit about the resource being 'Google Search Console search 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?

No guidance on when to use this tool versus alternatives like gsc_compare_periods or gsc_inspect_url. The description does not mention scenarios, prerequisites, or exclusions.

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