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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds two useful behavioral notes (free/beta tier, deliberately compact output), but 'compact' is never explained — the agent cannot tell what is truncated or whether the result is complete.

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 short fragments, front-loaded with the tier caveat and the core purpose — nothing wasted. It is arguably too terse for a tool with an undocumented parameter, but there is no filler.

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 one-parameter, no-output-schema tool whose annotations already cover safety, the description is close to adequate: it names the source, the key, and the compact nature of the return. It falls short on award-ID format and on what 'compact' excludes, which are the two things an agent would need to call and interpret it confidently.

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?

With a single required parameter and 0% schema description coverage, the description carries the burden; it does say the tool is keyed by award ID, but gives no format, source, or example of a valid award ID (the schema only enforces 1-200 chars). This is minimal compensation for the coverage gap.

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 verb (summarizing), resource (USAspending federal award), and access key (award ID), so the agent knows exactly what it retrieves. It does not distinguish itself from the sibling us_federal_award_evidence, leaving the basic-vs-evidence split to be inferred from the naming convention.

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?

'FREE beta' implies a cost/availability consideration but the description never says when to pick this over us_federal_award_evidence or what prerequisite (a valid award ID) it needs. Usage is only implied by the tool name pattern, not stated.

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