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

Annotations already declare readOnly/openWorld/idempotent, so safety is covered. The description adds non-obvious context the annotations cannot: a $0.01 USDC per successful call x402 payment on Solana and an equivalent HTTPS endpoint. It omits rate limits and result caps, which are discoverable only via schema defaults.

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-loaded with the core purpose, then filtering, then return contents, then pricing/endpoint. Dense but every clause carries information; the return-field enumeration is slightly long but helps fill the missing output 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 no output schema, the description compensates by enumerating returned fields (award id, recipient/UEI, amount, outlays, dates, agency, type, NAICS/PSC, link, total count). Payment model and endpoint are covered; pagination/result-size behavior is left to the schema.

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 every parameter is documented structurally. The description reinforces agency abbreviation formats (DOD, NASA, HHS) and the default date window but adds little beyond what the schema already states; 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/resource: 'Federal contracts, IDVs, grants, loans and direct payments from USAspending.gov', plus the filter dimensions and the returned fields. No sibling tool covers federal award spending, so an agent can route to it unambiguously.

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 by the resource described (query federal awards by recipient/agency/NAICS/keyword), and defaults (last 12 months) give useful context. However, it names no alternatives or exclusions and doesn't say when to prefer this over e.g. sec_edgar_search or federal_register for related federal data.

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