find_striking_distance_keywords

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds meaningful behavioral context: the ranking metric (estimated extra clicks if position 3 reached), default position range, impression threshold, and that rows below min_impressions are ignored. It does not mention authentication or data freshness, but the added context exceeds annotation coverage.

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?

A single front-loaded sentence defines the tool, followed by a compact Args list with defaults. Every sentence earns its place; no redundancy or filler.

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 an output schema present, the description needn't explain return values, and it covers purpose, ranking logic, and all parameters. It does not mention prerequisites such as GSC access or property permissions, but the openWorld annotation and site_url default provide sufficient context for correct invocation.

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 0%, so the description carries the full burden. It documents every one of the 6 parameters with meaning and defaults: site_url falls back to GSC_SITE_URL, days to analyse, position bounds, impression floor, and row limit. This fully compensates for the schema's lack of descriptions.

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 states a specific concept and action: 'quick wins: queries ranking just off the top spots' ranked by estimated extra clicks. It clearly conveys what the tool returns, though it does not explicitly differentiate itself from siblings like find_low_ctr_opportunities or get_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?

Usage is implied by the 'Quick wins' framing and the default position window, but there is no explicit guidance on when to use this tool versus alternatives, nor any stated exclusions. An agent must infer the right context from the name and description alone.

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