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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely new operational context: a $0.002 USDC charge per successful call via x402 on Base, Solana or Arc, with failed calls uncharged. It also discloses scope limits (contracts only, one agency, 1-365 day window) that the annotations cannot express. It does not describe pagination or result ordering, but the output schema covers the return shape.

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 first sentence is a tight, front-loaded statement of scope and return fields, and the pricing sentence is useful. However, the sibling-routing clause is long, ends in a garbled fragment ('from three official'), and consumes space without resolving the ambiguity it was meant to address.

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 an output schema present, return-value explanation is unnecessary, and the description covers what matters for invocation: agency scope, contracts-only restriction, day window, and cost model. The only real gap is that it does not clarify how this tool differs from gov_government_contract_awards, which is the main decision an agent faces.

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 three parameters including the 1-365 day range, 1-10 limit, and toptier agency naming. The description reinforces the toptier-name matching requirement and the day window but adds no syntax, format, or enumeration detail beyond the schema. 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 resource and verb-like scope: 'Largest US federal contract awards from USAspending.gov' for a single toptier agency over a bounded window, and it enumerates returned fields (award ID, recipient, amount in USD, start date). The 'largest ... from one agency' framing distinguishes it from generic search tools, but the distinction from the named sibling gov_government_contract_awards is not made explicit.

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?

It names two related tools and gives a 'when you need' condition, but the condition for gov_government_contract_awards ('when you need US federal contract awards from USAspending.gov') is essentially identical to this tool's own purpose, so an agent gets no real basis for choosing. The phrase about gov_global_tender_funding_watch is truncated ('from three official'), leaving that routing incomplete. The one hard prerequisite it does state is that the agency name must match USAspending's toptier name.

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