search_console_analytics_top_queries

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

No annotations are provided, so the description carries the full burden, yet it only states the action and shortcut. It does not disclose behavior such as optional site_url meaning 'single verified site', how 'top' is determined (e.g., sort order), pagination, or response format. This is a significant transparency gap.

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 description is a single concise sentence, front-loaded with the purpose, and the shortcut explanation is valuable. No redundant or filler content.

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?

As a simple wrapper tool with no output schema and no annotations, the description should clarify return values and scope. It says 'top queries' but does not define the metric or whether site_url is required. The shortcut reference provides some context but leaves meaningful gaps for an agent deciding on this 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?

Schema descriptions cover 100% of parameters, so the baseline is 3. The description does not add additional parameter-specific meaning beyond what the schema already provides, though it implies the tool is limited to the query dimension.

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 'Get top search queries for a site' with a specific verb and resource. The 'Shortcut for analytics.query with dimensions=['query']' note distinguishes it from the general analytics.query tool and from siblings like top_pages and device_breakdown.

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?

The description provides a clear alternative by noting this is a shortcut for analytics.query with a specific dimension, implying use when only query-level data is needed. However, it does not explicitly say when not to use it or contrast with top_pages/device_breakdown.

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