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

The annotations already declare readOnlyHint=true and openWorldHint=true, so this reads as a safe external-data read. The description adds genuine context: the data is from the official USAspending.gov source, and the output includes an AI summary, which is not visible in the structured fields. It says nothing about result caps, pagination, data freshness lag, or the cost of the AI summary step, and the sentence is cut off.

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 description is a single sentence repeated verbatim and truncated mid-phrase ("with an AI summary of a…"), which reads as a scraping artifact rather than authored text. The repetition wastes space and the cut-off leaves the key claim about AI summaries unfinished.

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?

The tool has no output schema, a nested free-form input object, and only annotations for safety. The description would need to carry the input shape and output shape, but it is truncated and explains neither. An agent still cannot tell what to pass or what comes back.

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?

Although the coverage metric reads 100%, the only schema entry is a free-form nested 'input' object whose entire description is a pointer to https://apify.com/noniner/us-gov-contracts. Neither the schema nor the description documents the actual search fields an agent must supply (keyword, agency, date range, NAICS, award amount), so the description does not compensate for what is effectively undocumented input semantics.

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 US federal contract and grant awards from USAspending.gov, with the content spelled out as "who won what, how much, from which agency." That distinguishes it well enough from siblings like eu_grant_finder, nordic_public_tenders, and us_funding_rounds. It stops short of naming a sibling it excludes, and the sentence is truncated and duplicated.

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 never says when to use this rather than related tools (eu_grant_finder for EU grants, us_funding_rounds for VC rounds, nordic_public_tenders for Nordic tenders). Usage is only implied by the resource name, and there is no exclusion criteria or example query.

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