gao_protest_lookup

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

Annotations declare readOnlyHint=true and openWorldHint=true. The description adds crucial context: the feed covers only ~25 items, results are incomplete (complete:false), and historical search requires a paid API. No contradictions.

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 fairly concise given the complexity, with key info front-loaded. It includes an 'HONEST SCOPE' section that clearly states limitations without being verbose. Minor redundancy but overall efficient.

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 no output schema, the description covers usage, filtering, enrichment, and limitations. It explains the fields returned (protester, agency, outcome, etc.) and when to expect nulls. Sufficient for effective tool selection.

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?

With 100% schema coverage, the baseline is 3. The description adds value beyond schema by explaining the limit's relation to feed size, the agency filter's scope, and bNumber's purpose to bypass the feed for aged-out decisions.

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 retrieves 'Recent GAO (Comptroller General) bid-protest decisions' from a specific RSS feed, enriched with details. It differentiates from unrelated sibling tools by focusing on GAO protests, with no overlap.

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 notes when to use (recent feed) and when not (historical search is WAF-blocked). It advises using bNumber for aged-out decisions and clarifies that results are always marked complete:false, guiding the agent on appropriate scenarios.

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