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

Annotations already cover safety (read-only, idempotent, non-destructive), so the bar is lower. The description adds useful behavioral context: output is normalized flat JSON with listed fields, category must be singular, date omission triggers the last-year default, and it complements get_opportunities. No contradictions with 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?

Three dense sentences: front-loaded with subject and source, then output shape, then usage rules. No filler, no redundancy with the schema, and every sentence earns its place.

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 the returned fields and explaining source, category, date, and workflow. Given 9 optional and well-documented parameters, nothing essential is missing; pagination is self-explanatory from 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?

All 9 parameters have schema descriptions (100% coverage), so the baseline is 3. The description mostly restates category values and date-default behavior already present in the schema, adding no new per-parameter semantics beyond broader workflow context.

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 and resource: retrieving federal spending awards from USAspending.gov, and immediately bounds the scope with award categories and the main output fields. It pairs with get_opportunities but does not explicitly contrast with the sibling get_grants, which weakens differentiation.

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?

Provides concrete usage rules: choose one category per call, omit dates to get the trailing year, and use alongside get_opportunities for the solicitation-to-award workflow. It does not explicitly state when to prefer get_awards over the get_grants sibling.

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