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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds meaningful interpretive context beyond that: signals are disproportionality statistics, not causal evidence, and the output is not medical advice — context that prevents an agent from over-claiming results.

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 core method sentence is front-loaded and dense with useful specifics; the two trailing caveats are short and earn their place as interpretation guards. No filler or repetition.

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?

An output schema exists, so return-value explanation is unnecessary, and annotations cover safety and idempotency. For a one-parameter read tool, the definition is nearly complete; the only real hole is the absence of sibling differentiation against get_drug_safety.

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 description coverage is 100% and the single parameter ('Drug brand or generic name') is documented in the schema itself. The description adds no format, synonym, or normalization guidance beyond that, so the 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 ('drug safety signal detection from FDA FAERS') and even names the statistical method (PRR, chi-square, Evans criteria), so the tool's function is unambiguous. However, it never distinguishes itself from the sibling get_drug_safety, which an agent could easily confuse with this detection tool.

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 states the output is 'a statistical prompt for study, not evidence of harm' and 'not medical advice,' but that is interpretive framing, not usage guidance. There is no when-to-use versus alternatives, and crucially no routing to get_drug_safety, get_drug_label, or list_fda_recalls for adjacent questions.

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