gsc_top_queries

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

With no annotations, the description carries the full burden for behavioral disclosure. It mentions the metric ('by clicks') but does not state that it is a read-only operation, that site verification is required, or that results are limited top queries only. The date range behavior is only in the schema, not in the description.

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 two sentences, front-loads the core purpose, and contains no redundant information. Every word contributes to understanding the tool's function.

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 simple shortcut tool, the description is adequate but does not clarify what is omitted relative to the full search analytics tool (e.g., custom dimensions, filters, grouping). Since there is no output schema, a bit more context about return format would improve completeness.

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 schema provides 100% description coverage for all parameters, so the baseline is 3. The description adds no additional parameter-level semantics; it simply confirms the main focus on top queries by clicks.

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 returns top search queries by clicks for a site, using a specific verb and resource. However, it does not explicitly differentiate from sibling tools like gsc_search_analytics or gsc_top_pages, causing minor ambiguity.

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 phrase 'convenient shortcut for common analysis' implies a simpler use case but does not explicitly state when to use this tool versus alternatives like gsc_search_analytics for custom queries. No exclusions or alternative recommendations are provided.

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