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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful content context by naming the returned dimensions (funding, programs, recent awards), but says nothing about match behavior, result limits, or scope beyond the schema.

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?

Two tight sentences that lead with the resource and preview the return content — no filler. The trailing 'Pairs with...' clause is a little fuzzy but very short, so it does little damage.

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 lookup with no output schema, the description covers the essential scope and the shape of the return signal (funding, programs, recent awards), and annotations carry the safety story. Match semantics and result limits are the only notable omissions.

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?

With a single parameter at 100% schema description coverage ('Awardee organization name (substring)'), the schema already documents the input. The description adds no additional meaning about the name parameter, so the baseline 3 applies.

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 clear resource (NSF Awards for one organization) and previews the payload (total funding, top programs, recent awards), which distinguishes it from the sibling nih_by_org. The verb is only implicit (carried by the title's 'Get'), keeping it just below a full 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?

The line 'Pairs with academic medical centers + biotech/tech startups' gestures at a domain but does not state when to use this tool versus alternatives like nih_by_org or patents_by_assignee. No when-to-use conditions, prerequisites, or exclusions are given.

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