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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds what the dossier contains, but omits that 'name' is a substring match that may resolve to multiple orgs, and says nothing about result size or pagination.

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 with zero filler; the resource scope and the returned payload are front-loaded before the audience hint.

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 no output schema, the description usefully names the key return fields, and annotations carry the safety profile. The main residual gap is ambiguity handling for a substring name search, which matters for a one-required-param lookup.

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 100% for the single 'name' parameter, so the baseline is 3. The description adds only the framing of 'one organization' and does not clarify substring behavior or how ambiguous matches are handled.

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 ('NIH RePORTER dossier for one organization') and enumerates the payload (total federal R&D funding, top activity codes, recent grants). It implicitly distinguishes itself from nsf_by_org via the NIH scope, but never names that sibling explicitly.

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?

'Best for academic medical centers + biotechs' hints at intended audience, but there is no when-to-use vs when-not guidance and no named alternative (e.g., nsf_by_org, company_profile, dossier) to route the agent.

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