gsc_striking_distance

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

With no annotations, the description explains the filtering logic (positions 4-20, sorted by impressions descending) and the low-hanging fruit concept. It does not mention destructive actions (none expected) or authentication details, but is generally transparent.

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 focused sentences with no wasted words. The main action and value proposition are front-loaded.

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?

No output schema is provided, and the description does not specify the fields returned (e.g., query, impressions, position). Given the complexity (7 params), an agent might need to infer output structure, leaving a completeness gap.

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 100% with descriptions for all 7 parameters, so baseline is 3. The description reinforces the default position range but adds no new information beyond the 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?

The description clearly specifies the verb 'find' and resource 'queries ranking in positions 4–20', and the term 'striking distance / low-hanging fruit' uniquely identifies the tool's niche among siblings like gsc_search_performance.

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 states these queries are 'best candidates for quick ranking improvements', implying when to use. However, it does not explicitly exclude alternatives or provide when-not-to-use guidance.

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