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

Annotations already convey read-only, idempotent, and non-destructive behavior. The description adds useful context by disclosing fuzzy matching, a 4-hour cache, USASpending.gov as the verified source, and the categories of data returned. One small gap is that it does not clarify how a single US source relates to the EU and UK jurisdiction options.

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 dense but economical, front-loading the core action and then adding safety, source, cache, output, and routing details. It is slightly long because it repeats some annotation facts, but no sentence is pure filler.

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?

With an output schema present and only two simple parameters, the description covers everything needed for invocation: purpose, routing, source reliability, caching, matching behavior, and a feedback fallback. An agent can call this tool correctly without looking elsewhere.

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 schema already documents both parameters. The description adds meaningful behavioral detail by stating that fuzzy matching is applied to vendor_name, which helps the agent set expectations for imprecise company names.

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 opens with a specific verb and resource: Fetch the complete federal contract award history for a specific vendor. It also clearly distinguishes itself from govcon_search_contract_awards by framing this as vendor-specific lookup rather than topic exploration.

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?

It explicitly says to use this tool when researching a specific company's government contracting history and to use govcon_search_contract_awards instead for topic-area exploration. This gives an agent direct routing criteria and names the relevant alternative.

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