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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, and the description adds real value on top: it enumerates what is returned (bounded award amounts, dates, investigators, org ids, project links, source hashes) and flags explicit limits and excluded fields (abstracts, contacts). What the 'explicit limits' actually are remains unquantified.

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 dense sentences, front-loaded with the action and resource; every clause carries information (facets, output contents, exclusions). The second sentence is long but not padded.

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 an output schema and full safety annotations present, the description need only add routing and boundary information, which it does well. Minor gap: the concrete bounds/limits implied by 'explicit limits' and how max_results is capped are left implicit.

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 coverage is 50%: query and organization are documented in the schema, while fiscal_year and max_results are not. The description maps 'topic' to query and 'institution' to organization and mentions fiscal year, but adds no format or semantics for fiscal_year (fiscal vs. calendar) and says nothing about max_results or the interaction between the anyOf required groups.

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 ('Search official NIH RePORTER research-award administrative metadata') plus the search facets (topic, institution, fiscal year). No sibling covers NIH awards, so an agent can route here without ambiguity.

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 implies when to use it (looking up NIH award records by topic/institution/year) and notes that abstracts and contact details are out of scope, but it names no alternative tools or conditions for choosing between them. Usage is inferred rather than stated.

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