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

Annotations already provide destructive, idempotent, and open-world signals, and the description adds useful behavioral context: it returns a manifest with official URLs but does not read or analyze the documents themselves. It does not mention auth, rate limits, or whether data is live/cached, but the openWorldHint and non-contradictory annotations lower the burden.

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 three tightly written sentences with no filler. The trigger condition is front-loaded, the return scope is specific, and the exclusion list is compact and highly informative.

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 description covers purpose, scope, exclusions, and return contents, and an output schema exists to document return values. A small gap is the lack of explicit notes on authentication or error/empty-result behavior, but for a single-parameter manifest tool this is largely sufficient.

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?

The single parameter has 100% schema coverage, including a pattern, min/max length, and a clear description of opportunity_id as an official Grants.gov ID. The tool description reinforces the grant-opportunity context but adds no parameter-specific semantics beyond the schema, so baseline 3 is appropriate.

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 description clearly states that the tool returns a manifest of official documents for a U.S. federal grant opportunity, including current revisions and completeness status. It names specific document types and download URLs, and the 'does not read/assess/predict/draft/submit' clause helps distinguish it from analyze and submit siblings.

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?

It opens with an explicit 'Use this when the user needs to know...' trigger covering document lists, revision currency, and completeness. It also explicitly lists what the tool does not do, so an agent knows not to use it for reading documents, eligibility assessment, award prediction, drafting, or submission.

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