gsc_query_search_analytics

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds return metrics (clicks, impressions, CTR, avg position) and mentions flexibility, but no behavioral contradictions. Description adds value 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?

Two brief paragraphs front-loaded with purpose and usage guidance. No redundant information. Every sentence serves a purpose.

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?

Given the tool's flexibility and the presence of an output schema, the description covers the essential aspects: purpose, when to use, return values. Could mention pagination or default date range, but schema covers those. Adequate for a complex tool.

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?

The input schema has detailed descriptions for each parameter, so description doesn't need to cover them. It hints at 'multi-dimensional grouping' and 'non-default search types' which relate to dimensions and search_type parameters, but doesn't add significant new meaning.

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 runs a flexible Search Analytics query. It distinguishes itself from siblings by specifying that it is for multi-dimensional grouping and non-default search types, referencing convenience tools gsc_top_queries and gsc_top_pages.

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?

Provides explicit guidance: 'For common cases, prefer the convenience tools... Use this tool when you need multi-dimensional grouping or non-default search types.' This clearly tells when to use and when not to use.

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