find_striking_distance_keywords

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds real value beyond that by disclosing the interpretation caveat that ranking position alone does not determine improvement effort — behavioral context the annotations cannot express.

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?

Front-loaded with the definition of the target keywords, followed by a useful caveat, then a compact Args block. The Args list duplicates schema names but is justified given 0% schema coverage, and every sentence carries 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?

With an output schema present, return values need not be described, and the description covers purpose, interpretation caveat, and all four parameters with defaults. It is close to complete for this tool's complexity.

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 must carry parameter meaning, and it does: it documents all four args with their roles and defaults (days=28 lookback, min_impressions=10, row_limit=50, exact GSC property URL). Minor gaps remain (units, URL format specifics), but it largely compensates for the empty schema.

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?

States a specific verb and resource and concretely defines the domain term 'striking distance' as queries ranking at positions 5-20 with decent impressions. It doesn't explicitly differentiate from siblings like get_search_analytics or detect_cannibalization, but the scoping detail is strong enough that an agent can identify it.

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 caveat 'These are review candidates; positions alone do not establish the effort needed to improve rankings' implies the tool produces candidates for review rather than final decisions, but it gives no explicit when-to-use vs alternatives guidance or prerequisites beyond the required site_url.

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