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

Annotations only declare readOnlyHint and openWorldHint, so the description usefully adds the paid-call model ($0.002 USDC via x402, failures free), the coverage caveat that only awards reported to USAspending appear, and the fixed retention window — all decision-relevant beyond the annotations. It omits rate limits and matching/fuzzy behavior for recipient names.

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?

Three sentences, zero filler: data scope first, exclusions second, pricing last. Front-loaded with the most agent-relevant facts and no repetition of the title or schema.

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, the description does not need to enumerate return fields, and annotations cover safety. Source, scope, exclusions, window and cost are all covered; only edge-case behavior (no-match results, recipient-name matching semantics) is left unstated.

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 short, clear descriptions for both `recipient` (3-100 chars) and `limit` (1-10, default 5), so the schema already carries parameter meaning. The description only reinforces that the query is by recipient name over a fixed window; it adds no syntax or matching-behavior detail beyond the schema.

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+resource (federal contract awards), the upstream source (USAspending.gov), the fixed time window, and the exact returned fields. It explicitly rules out grants and loans, which cleanly separates it from siblings like gov_grants_gov and gov_sbir_government_grants.

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?

Explicit exclusions ("Contracts only (not grants or loans)") and a stated 365-day lookback give an agent clear positive and negative usage conditions. It stops short of naming an alternative tool to call instead, so routing is inferred rather than directed.

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