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

With no annotations, the description carries the full burden and delivers: it discloses latency/cost behavior (hits Google every call), that position is impression-weighted rather than a rank-tracker rank, that deep positions rest on sparse data, and that absolute positions should be treated as directional. It also spells out pagination semantics and the meaning of 'truncated' for drawing conclusions.

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?

Purpose is front-loaded and POSITION/PAGING headers organize the caveats well. It runs long for a single tool, but nearly every sentence contributes interpretation guidance or a routing rule, so the density is justified rather than padding.

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?

There is no output schema, so the description must explain returns, and it does: the pagination block fields (returned, total_available, truncated, next_offset) and how to interpret them are described. Combined with the threshold and position caveats, an agent has everything needed to call and read this tool correctly.

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 83%, so most parameters are already documented and a baseline of 3 applies. The description adds meaning beyond the schema by framing max_position/min_impressions as user-tunable thresholds and clarifying the limit/offset paging loop (pass next_offset, or raise limit), which is more than the schema alone conveys.

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: queries sitting just off page one with enough impressions to matter, and explicitly positions itself against the sibling SEO_Insights as the 'live, tunable counterpart'. An agent can distinguish it from the other ~30 opportunity tools without opening a schema.

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?

Names the alternative (SEO_Insights) and the exact condition selecting this one: live Google data with user-set thresholds, at the cost of being slower. The tradeoff ('slower because it goes to Google on every call' vs 'thresholds are yours to set') gives the agent a clear routing rule.

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