quick_wins

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

With no annotations, the description carries the full burden and does well: it discloses that position is an impression-weighted average, not a rank-tracker rank, that deep positions rely on sparse data, and that absolute positions are directional. It also imposes clear analysis constraints against speculation and requires artifact-based visual presentation, which are behavioral traits an agent must know.

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?

The description is longer than average but well-structured with clear IMPORTANT, PRESENTATION, and POSITION sections. It front-loads the core purpose and each section adds actionable guidance, though the presentation block is somewhat verbose and could be tightened.

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?

For a low-complexity tool with three optional parameters and no output schema or annotations, the description covers purpose, result semantics, data caveats, and output presentation. However, it lacks exact response fields, pagination behavior, and explicit usage alternatives, which prevents it from being fully complete.

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%, so the baseline is 3, but the description adds meaningful context: 'positions 4-15' and 'high impressions' map to max_position and min_impressions, while 'traffic opportunity' explains the sorting intent. It also clarifies that the position value is blended and directional, which enriches the meaning of the position-related parameter.

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 states the tool finds keywords 'almost ranking for' page one and returns queries at positions 4-15 with high impressions, sorted by traffic opportunity. This is specific and distinguishes it from image_search_quick_wins, though it does not explicitly name sibling alternatives or exclusion criteria.

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 gives strong analysis and presentation instructions but no explicit guidance on when to choose quick_wins over siblings like ctr_opportunities, content_gaps, or image_search_quick_wins. Usage context is implied by the name and first sentence, but there are no exclusions, prerequisites, or alternative tool references.

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