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

Annotations already declare readOnly/openWorld/idempotent, but the description still adds substantive behavior: a 25-award cap per competitor, name matching by text that may pull in subsidiaries, a date floor of 2007-10-01 through today UTC, and — most importantly — that failed items do not block successful competitors from returning. That partial-failure semantics is exactly what an agent cannot infer from structured fields.

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?

Front-loads the trigger and the core action before limits and exclusions, with no filler sentences. Some sentences are clause-stacked and read more like a spec dump than prose, which slightly hurts scanability, but every clause carries 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 zero-required-parameter tool with 9 filters, an output schema, and full annotation coverage, the description supplies the trigger, the limits, the date window, and the failure model. Nothing an agent needs to select or invoke it correctly is missing.

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, and the description goes beyond it by stating the 1–10 competitor bound and that name matching includes subsidiaries, which changes how a caller should format names. The remaining filters (naics, psc, agencies, states) are left entirely to the schema, which is reasonable given full coverage.

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 (looks up live public federal awards for competitors and builds an Excel comparison) and frames the intent (award history, recompete research). The exclusive clause 'Do not use for corporate identity verification, open solicitations or bids' separates it from the neighboring search tool without ambiguity.

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?

'Use this when...' plus an explicit 'Do not use for...' gives both a positive and a negative trigger, which is more than most tool descriptions offer. It stops short of naming the sibling search_contract_awards as the single-name lookup alternative, so the routing choice at the tool boundary is left slightly implicit.

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