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

No annotations are provided, so the description carries the full burden. It does add meaningful interpretive context — the signal definition and the explicit caution that a signal is not evidence of harm or medical advice — but it says nothing about return format, data recency, or FAERS reporting limitations, which an agent would need for a read tool with no structured safety hints.

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 core purpose and method, then the caveats; every sentence carries substance and there is no filler. It is appropriately sized for a one-parameter tool.

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 annotations and no output schema, the description must stand alone. It adequately conveys what the tool computes and how to read the result, but it omits output shape and, more importantly, any discrimination from the near-identical health_drug_safety sibling.

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 'drug' parameter whose schema description already covers it at 100%. The description adds no format guidance (brand vs generic, casing, multi-drug input), so the baseline 3 applies rather than a higher score.

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 names a specific resource (FDA FAERS drug safety signals) and a precise method (proportional reporting ratio and chi-square with Evans criteria), which is far beyond a tautology. However, it never distinguishes itself from the very similarly named sibling health_drug_safety, leaving an agent unable to tell the two apart from the text alone.

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?

There is no statement of when to use this tool versus alternatives such as health_drug_safety, health_drug_label, or health_drug_approvals. The closing caveats ('a statistical prompt for study, not evidence of harm. Not medical advice.') frame interpretation but do not provide routing guidance.

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