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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds real interpretive context beyond them: the data source (FDA FAERS), the caveat that reports are not proof of causation, and that it is not medical advice — meaningful for correctly framing the numbers to a user.

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?

Front-loaded with the resource and its contents in one dense sentence, followed by two short disclaimer clauses that each earn their place by preventing causal misreading. Slightly list-heavy but no wasted filler.

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 present and full parameter coverage, the description need not explain return values, and it still names the fields and source. The only missing piece is guidance on how it relates to the sibling drug tools.

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?

There is a single required parameter at 100% schema description coverage, so the schema already carries the specification. The description's '(brand or generic name)' simply restates the schema's own parameter description, adding no new syntax or format detail. 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?

The description gives a specific verb+resource ('FDA drug safety snapshot') and enumerates the concrete payload (total adverse event reports, serious/fatal share, top side effects, quarterly trend from FAERS). It does not, however, distinguish itself from the sibling detect_drug_safety_signals or list_drug_approvals, so an agent must infer the boundary.

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?

Usage is only implied by 'for any drug (brand or generic name)' — the agent is told what input it accepts but not when to prefer this over detect_drug_safety_signals or get_drug_label. No exclusions or alternative routing are stated.

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