seo_striking_distance

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

With no annotations, the description carries the full behavioral burden. It discloses the result-set definition (positions 8-15, sorted by impressions desc), which is useful, but says nothing about result limits, pagination, or whether the position band is fixed versus configurable. An output schema exists, so return shape is reasonably covered elsewhere.

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 short sentences, with the concrete scope (position range + sort) front-loaded before the rationale. Efficient and easy to scan, though the second sentence is motivational padding rather than operative 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?

An output schema exists so return values need not be explained, and the core filter is stated. But with 0% parameter coverage and no differentiation from quick_wins, an agent lacks enough to confidently choose and configure this tool.

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% and none of the four parameters (days, site, engine, min_impressions) are mentioned or explained in the description. The 8-15 range it does describe is a hardcoded output filter, not a parameter, so the description adds essentially no parameter-level meaning over the bare 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 (list) and resource (queries) with an explicit position band (8-15) and sort order, so the agent knows exactly what comes back. However, it never distinguishes itself from the very close sibling quick_wins, which plausibly returns the same 'striking distance' concept, leaving ambiguity about which tool to pick.

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?

It explains the analytical intent ('best candidates for ranking improvement'), which implies when the tool is useful. But it gives no explicit when-to-use versus alternatives and does not address the overlap with quick_wins or get_advanced_search_analytics, so the selection guidance is only implied.

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