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

With no annotations the description carries the full burden and does substantial work: it discloses the fixed nine-case sample size, that original stage is preserved, that 'recommended/ranked' does not imply 'awarded', and that results are neither exhaustive nor live. It omits anything about result shape or ordering, but the semantic caveats an agent would otherwise get wrong are covered.

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 tight sentences, front-loaded with the scope and followed by the disclaimers that prevent misuse. No filler; every clause carries decision-relevant 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?

For a read-only search with no output schema and no annotations, the description supplies the essential framing: bounded sample, preserved stage semantics, and non-live status. It stops short of describing return fields or ordering, which an agent might reasonably want, but the critical interpretive context is present.

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 100%, so the schema already documents all three parameters, including the tier-capped limit and stage examples. The description adds nothing parameter-specific (e.g., valid stage values or keyword matching behavior), so baseline 3 applies.

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 — searching nine source-linked historical public procurement research cases — and enumerates the case contents (rubrics, committee scores, rankings, awards). It distinguishes itself from live/complete datasets but never names the closest sibling, contracts_search_bid_outcomes, so the boundary requires inference.

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?

Usage is implied rather than stated: the 'hand-selected research sample, NOT a complete bid universe or live SMAT outcomes' warning tells the agent when NOT to rely on it, but there is no explicit routing to alternatives such as contracts_search_bid_outcomes or contracts_search_awards.

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