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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered. The description adds genuine context beyond them: the upstream source (USAspending.gov), the sort order (by amount), and the returned field set, which is valuable since no output schema exists.

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?

Two sentences, front-loaded with purpose and scope, then the return contract. No filler or redundancy; every clause carries information the caller needs.

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 read-only, open-world search with full schema coverage and no output schema, the definition supplies what is missing: data source, sorted-by-amount behavior, and the exact result fields. An agent has everything needed to call it correctly.

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 already documents all seven parameters with examples. The description restates the filterable fields (recipient, keyword, agency, fiscal year, minimum amount) without adding syntax, defaults, or combination semantics beyond what the schema provides.

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 (Search) and resource (federal awards: contracts, grants, loans), names the data source (USAspending.gov) and the filterable dimensions, so the agent knows exactly what is retrieved. It is clearly a search tool distinct from spending_award_details, but it never names or contrasts with that sibling explicitly.

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?

Filter options imply when the tool is useful (by recipient, keyword, agency), but there is no explicit when-to-use guidance, no exclusions, and no pointer to spending_award_details for single-award lookups or spending_recipient_summary for aggregates. Usage is left to inference.

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