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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world scope are covered structurally. The description adds only 'Full details', which hints that the response is comprehensive rather than a summary, but it says nothing about a nonexistent-ID behavior, external API latency, or rate limits.

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?

A single short sentence with no filler, and the scope word 'one' is front-loaded. Slight deduction because it is a noun fragment rather than a complete assertion of what the tool does.

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 single-parameter read-only fetch with no output schema, the description is adequate but thin: 'Full details' gestures at return breadth without telling the agent what kind of information (deadlines, eligibility, award ceiling) comes back. An agent can call it correctly, but cannot decide between it and grants_search on content grounds alone.

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?

One parameter with 100% schema description coverage, so the schema already documents opportunityId as the Grants.gov opportunity id. The description contributes no additional syntax, format, or sourcing guidance, which is the baseline case when the schema does the work.

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?

Names the resource (a Grants.gov opportunity), the scope ('one'), and the depth ('full details'), which distinguishes it from the sibling grants_search that returns multiple results. It lacks an explicit verb ('retrieve'/'fetch'), which is the only reason it isn't a 5.

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?

Usage is only implied: 'one ... opportunity' signals a single-record lookup taken after a search, and the required opportunityId reinforces this. It never names grants_search as the way to obtain that ID, and gives no when-not-to-use guidance.

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