gsc_query_queries

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds the grouping behavior, which is useful, but it does not disclose pagination, maxRows limits, dataState variations, or return format. This provides minimal extra behavioral context beyond the 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?

The description is a single, tightly written sentence with no redundant or filler content. It is front-loaded with the action and resource, making it immediately scannable.

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?

With 9 parameters, no output schema, and the presence of many sibling tools, this one-sentence description is insufficient. It doesn't mention typical response metrics, filter capabilities, row limits, or usage scenarios. The schema provides defaults and enums but not semantic meaning, so the tool is only minimally contextualized.

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 11% (only siteUrl is described). The description does not explain filters, date format, maxRows, dimensions, or aggregationType. It only implies 'query' as the grouping dimension, aligning with the schema default, so it fails to compensate for the low schema coverage.

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 'Query Search Analytics grouped by search query' clearly states the verb (query), resource (Search Analytics), and the grouping dimension (search query). This effectively distinguishes it from sibling tools like gsc_query_pages and gsc_query_countries, though 'query' as a verb is slightly generic.

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 no explicit guidance on when to use this tool versus alternatives such as gsc_search_analytics, gsc_top_queries, or gsc_query_pages. Usage must be inferred from the tool name and siblings, with no exclusions or context given.

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