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

Annotations already cover readOnly/idempotent/non-destructive safety, so the bar is lower. The description adds real value beyond them by declaring the temporal window ('current signal window'), the returned fields, and an explicit negative scope (excludes ClinicalTrials.gov device trials, Breakthrough marketing authorizations, HDE approvals).

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?

Purpose is front-loaded, followed by filter guidance, return fields, and exclusions. Every sentence earns its place, though the final exclusion list is somewhat long and listy.

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 compensates by enumerating the return payload (company, phase, amount, date, source) and clarifying boundaries via the negative scope. Combined with annotations covering safety, an agent has enough to call it correctly.

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 100%, so baseline is 3, but the description goes slightly beyond the schema by explaining the rationale for new_award ('where programs are still choosing partners') and restating the phase distinction and amount threshold in plain language.

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 resource and scope: 'NIH awards in the current signal window.' An agent can tell this is a funding-event query. However, it never explicitly distinguishes itself from signal-oriented siblings such as find_signals, latest_signals, or signal_of_the_day.

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?

It explains how to use each filter (pass new_award/phase/min_amount_usd to narrow), which implies usage, but gives no when-to-use-this-vs-alternative guidance or exclusions relative to the many signal siblings. The 'current signal window' phrase is the only scoping hint.

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