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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds the shape of the result (obligated total plus three counts), which is mild added value since an output schema exists; it says nothing about auth, pagination, or empty-award behavior.

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?

Three short front-loaded sentences with the core purpose first and the return fields enumerated second. The field list is slightly redundant with the output schema but not wasteful.

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 and rich read-only annotations, the description is close to self-sufficient for invocation. The remaining gap is identifier format for award_id, which is the one thing an agent could get wrong before calling.

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% for the sole required parameter award_id, and the description only says 'a single award' — it never clarifies whether this is a generated award ID, a PIID, or a URI, despite siblings like lookup_piid implying identifier formats matter here.

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 and resource: a rollup of an award's funding totals, plus the exact aggregate figures returned. It distinguishes itself in spirit from get_award_funding/get_award_detail via 'one-line summary', but never names those siblings explicitly.

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?

'Useful for a one-line summary of an award's funding picture' implies the use case but gives no explicit when-to-use vs when-not, and does not route to the obvious alternatives (get_award_funding, get_award_federal_account_count, get_award_detail) in a crowded sibling set.

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