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

Adds substantial operational context beyond annotations: beta status, guaranteed no-payment behavior, global daily capacity, the fact that only newly released complete results count against capacity, and request_id reuse for retries. These operational traits (payment, rate limiting, retry semantics) are exactly the kind of behavioral detail annotations cannot convey, and nothing contradicts the idempotentHint=true / readOnlyHint=false annotations.

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?

Four sentences, each carrying distinct information: purpose and usage trigger, payment safety, capacity and retry semantics, and exclusion boundaries. Purpose is front-loaded and there is zero redundancy with the schema or annotations.

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 annotations covering idempotency, the description covers the critical operational concerns: when to use it, payment safety, capacity constraints, retries, and non-goals. Minor gaps remain — what happens when daily capacity is exhausted and a gloss for the jargon 'hard-gate' — but nothing that would prevent an agent from invoking it correctly.

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 67%, leaving the nested organization object undocumented in the schema. The description adds only marginal parameter meaning: it reinforces request_id retry semantics already stated in the schema, but gives no guidance on opportunity_id or the organization sub-fields. The schema carries most of the parameter explanation burden.

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: retrieving a 'complete, versioned hard-gate and award-history evidence pack for one U.S. federal grant.' It is scoped to a single grant and explicitly differentiates from the search/analyze siblings by positioning itself as the post-search, pack-delivery step.

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?

Provides an explicit trigger condition ('after search or preview when the user wants a complete... evidence pack') and a strong exclusion list ('does not evaluate semantic project relevance, determine legal eligibility, predict an award, draft, or submit'). However, it never names the sibling tools (analyze_federal_grant, search_federal_grants) that would handle those excluded cases, so routing is implied rather than explicit.

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