find_low_competition_lanes

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context: it does not estimate win probability, returns only top-ranked lanes (with limit), provides total count in coverage.lanes_ranked, sources data from TED with CC BY 4.0, and gives no guarantee. No contradiction with annotations.

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 concise—three sentences covering purpose, exclusion, and output details. It is front-loaded with the key function and uses parentheses effectively. No wasted words.

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?

Despite lacking an output schema, the description sufficiently explains the return shape (top-ranked lanes, total count in coverage.lanes_ranked). It covers metrics, data source, and limitations (no guarantee). For a read-only data tool with two parameters, this is 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% with descriptions for both parameters. The description enhances meaning by explaining 'limit' as number of top lanes and adding context for 'min_n' with 'honest: small n = noise'. It goes beyond the schema by framing these parameters in the tool's purpose.

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 verb 'Rank' and the resource 'CPV sector lanes', and defines the specific metrics (median bidders, single-bidder share, etc.). It answers the question 'where is competition thinnest right now', distinguishing it from the sibling tool 'find_winnable_lanes' which focuses on win probability.

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 explicitly states what the tool does (rank by competition density) and what it does NOT (estimate win probability). It gives context that this is a data/research tool and mentions the limit parameter. However, it does not explicitly say when to use this versus alternatives, though sibling tools are listed and the purpose distinction is clear.

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