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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds valuable context beyond annotations by specifying the data source (api.nsf.gov) and explicitly stating 'no auth required', which an agent needs to know before invoking.

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 two sentences with no filler: the first sentence delivers the action and content, the second covers data source and authentication. Every sentence earns its place, and key details are front-loaded.

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 only one parameter, rich annotations, and an output schema present, the description covers all essential operational context: what the tool returns, the data source, and authentication requirements. Nothing critical is missing for correct invocation.

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 input schema already documents the single required parameter with a concrete example and provenance, so schema coverage is 100%. The tool description only refers to 'award ID' without adding format or usage details beyond what the schema provides, matching the baseline for high schema coverage.

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 states a specific verb ('Get'), a precise resource ('full detail for a single NSF research award'), and the key identifier ('award ID'). It also enumerates the included content (abstract, PI/co-PI contacts, program officer, etc.), distinguishing it from the nsf-awards.grants.search sibling by scope and specificity.

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?

The description makes clear it is for retrieving a single award when an award ID is already known. The parameter description further reinforces the workflow by noting the ID is obtained from nsf-awards.search results, providing clear context without explicitly stating exclusions.

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