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

Annotations already mark the tool as read-only, idempotent, and non-destructive, so the description is not burdened with explaining safety. It adds useful behavioral context beyond annotations by specifying the data source, the returned fields per award, and the sort order by amount. This exceeds the baseline while remaining consistent with the annotations.

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 a single, tightly written sentence that front-loads the tool's core purpose before listing filters and output fields. Every clause contributes useful information, with no filler or redundancy.

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?

Despite having no output schema, the description explicitly lists the returned award fields and sort order. Combined with the fully documented input schema and safety-bearing annotations, an agent has enough information to select and invoke the tool correctly. Nothing essential for using this search tool 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 description coverage is 100%, so the schema fully documents each parameter. The description adds some semantic value by grouping the primary filters as 'by recipient company, keyword, and/or awarding agency' and labeling fiscal year and minimum amount as optional. However, it does not substantially enrich parameter meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 action and resource: 'Search federal awards (contracts, grants, loans) from USAspending.gov'. It enumerates the available filters and the exact returned fields, making the tool's purpose immediately clear. It also differentiates itself from sibling spending tools by emphasizing plural award search and per-award returned rows rather than a single award detail or recipient summary.

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?

The description clearly conveys when to use this tool: when you need to find federal awards by recipient, keyword, agency, fiscal year, or minimum amount. It does not explicitly mention alternatives such as spending_award_details or spending_recipient_summary, and it provides no exclusion criteria, but the search-oriented framing and filter list give adequate contextual guidance.

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