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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds only that the response is 'richer' and avoids 'an unbounded raw passthrough' — a vague, unquantified claim about output size rather than concrete behavior such as rate limits, latency, or beta stability.

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?

It is short and front-loaded with the 'FREE beta' status, so it is not verbose. However, several sentences are marketing framing ('avoiding an unbounded raw passthrough', 'Intended future paid tier') that convey little operational value.

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?

There is no output schema, so the description should explain what 'evidence' and 'provenance' return, yet it does not. Combined with zero parameter documentation and no sibling differentiation, an agent lacks what it needs to confidently call this tool over us_federal_award_basic.

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 0% and the single parameter award_id is never mentioned in the description, so no format guidance is given (e.g. USAspending award ID vs. internal ID, expected string shape). Only the parameter's self-describing name carries any meaning.

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 phrase 'Richer USAspending award evidence and provenance' names the resource (USAspending award evidence) but uses no verb describing what the tool actually does, and it never explicitly contrasts itself with the sibling us_federal_award_basic. An agent can infer a tiering from the name pattern but not from the text.

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 says nothing about when to choose this over us_federal_award_basic or the other *_evidence siblings. 'FREE beta' and 'Intended future paid tier' are pricing/commercial notes, not usage guidance, so the agent gets no selection criteria.

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