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

No annotations exist, so the description carries the full burden. It usefully discloses the upstream source (USAspending.gov) and that results are ranked by size ('largest'), which signals a read-only lookup with sorted output. It does not disclose the default time window, pagination/limit behavior, or rate/quota constraints of the upstream API, leaving real gaps for a data-fetch tool.

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 tightly packed sentences: the first front-loads capability, source and output fields; the second gives the use case. No filler, no 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?

An output schema exists, so return values need not be explained, and the default award_type and time scoping are the main missing pieces. For a five-parameter tool with zero schema descriptions and zero annotations, the definition is workable but not sufficient to call confidently without inspecting the schema defaults.

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 coverage is 0%, so the description must compensate, and it partially does: 'keyword or recipient' maps to q and recipient, and 'contracts, grants or loans' supplies the candidate values for the otherwise unconstrained award_type string. It says nothing about 'days' (default 365-day window) or 'limit', so two of five parameters remain undocumented.

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 names a specific resource (US federal contracts, grants, loans), the source (USAspending.gov), the retrieval axis (largest by keyword or recipient) and the fields returned (recipient, amount, agency, dates, place, NAICS). It is distinguishable from nearby siblings like federal_register or us_company_filings by domain and data source, though it does not explicitly contrast with them.

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 offers a concrete use case ('B2G sales research or due diligence'), which implies the intended context. However, there are no when-not conditions, no mention of alternatives for company-level data (us_company_profile) or regulatory data (federal_register), and no statement of prerequisites.

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