top_queries

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

The description adds a meaningful behavioral quirk beyond the readOnly/openWorld/idempotent annotations: the default window ends three days ago because an ending-today window reads as empty due to Search Console lag. This is useful operational context that is not available in the annotations or schema.

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 sentences with no filler. The first states the core function and metrics, and the second justifies the default date window with a concrete reason. Every clause earns its place.

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?

The description names the returned metrics and explains the freshness default, which is important because there is no output schema. Combined with the very detailed parameter schema, an agent can call this correctly, though it does not fully discuss result ordering, pagination, or how it differs from related report tools.

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 high (86%), and the schema already explains site, type, account, country, and page_filter with useful detail. The main description does not explain any parameters itself, which is acceptable here because the schema carries the semantic burden.

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 identifies the resource: search queries ranked by clicks to a property, with a specific set of metrics (impressions, CTR, average position). It is clear enough to be distinguished from pages-focused siblings, though it does not explicitly name or contrast itself with top_pages or query_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?

The description explains default behavior and a data-lag reason, but provides no guidance about when to choose this tool over query_search_analytics, top_pages, or compare_periods. There are no exclusions or alternative routing cues, leaving the choice to inference.

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