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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is known. The description adds the key context that results are aggregate annual summary counts from official reports, not detailed case-level data. This is useful but minimal; no additional behavioral traits like pagination behavior or data freshness are disclosed.

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 fluff. The first sentence front-loads the exact action and resource, and the second adds essential scope clarification. Every word earns its place.

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?

Given the 7 optional parameters, full schema coverage, and helpful annotations, the description provides enough context: the data source, granularity, and topic area. It lacks an explicit return-value structure, but the lack of an output schema is mitigated by the clear 'summary counts' phrasing. A brief note on return format would make it fully complete.

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 covers 100% of parameters with descriptions, so the baseline is 3. The tool description does not add any extra parameter-level meaning beyond what the schema already provides, so the score stays at the baseline.

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 clearly states the tool searches for FDA's Biological Product Deviation Report annual summary counts, using specific verbs and resource names. It also distinguishes from per-event case detail, which uniquely identifies its scope among the many FDA search tools.

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 provides clear context on data granularity (summary-level vs. per-event) and explicitly notes what the tool does not do ('not per-event case detail'). However, it does not name an alternative tool for per-event searches, so it stops short of the explicit alternative guidance that would earn a 5.

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