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

With no annotations, the description carries the full behavioral burden. It usefully discloses that results come from the live USAspending.gov federal source, hinting at an external API call, but it says nothing about rate limits, latency, auth, result freshness, or pagination behavior and that the limit caps at 25 (only visible in the schema).

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 source, with zero filler. The second sentence's use cases slightly restate what the type parameter enum already conveys, but the overall length is appropriate.

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 6-parameter tool with no required params, no annotations, and no output schema, the description omits meaningful detail: how the type value governs which other parameters matter, what each mode returns, and how limit interacts with results. It is adequate but leaves real gaps for correct invocation.

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 parameters are already documented and the baseline is 3. The prose loosely ties recipient and agency concepts to use cases, but it does not clarify which parameters apply to which type value (e.g., that recipient is only meaningful when type=recipient), so it adds little 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?

It states a specific verb and resource ("Search federal award spending data") plus the data source (USAspending.gov) and three concrete modes (keyword search, company totals, agency breakdown). It is clear on its own, but it never distinguishes itself from the siblings search_awards, search_contracts, and search_grants, which appear to overlap heavily with its "awards" mode.

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 implies usage by mapping scenarios to the three type modes, which is helpful context. However, it gives no explicit when-to-use versus search_awards/search_contracts/search_grants, and no exclusions or prerequisites, leaving the agent to guess against three similarly named siblings.

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