gsc_query_gaps

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

Description adds sorting behavior (by impressions descending) and selection criteria beyond the readOnlyHint and other annotations. It does not contradict annotations and provides useful context without major gaps.

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 wasted text. Directly states purpose, selection criteria, and sorting. Front-loaded with key information.

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 5 parameters, no output schema, and many sibling tools, the description is fairly complete. It explains what is returned and the sorting, though it could mention typical use cases for output.

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 coverage is 80% (4 of 5 parameters described). The description does not add significant extra meaning for parameters beyond what the schema provides, and it does not clarify the undocumented site_url parameter.

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?

Description clearly states the tool returns queries with high impressions but low clicks, identifying content opportunity signals. It uses a specific verb-resource combination and implicitly distinguishes from sibling tools like gsc_top_queries.

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?

Description implies when to use: to find content opportunities where impressions exist but clicks are lacking. However, it does not explicitly state when not to use or mention alternatives, though the context is clear.

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