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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description does not contradict them. It adds useful context that the data comes from spontaneous FAERS reports and that each result represents a reported adverse reaction, which helps the agent interpret the returned data correctly.

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 compact and front-loaded, leading with the resource and scope before describing result contents and use case. The third sentence about pharmacovigilance is slightly generic but still earns its place as selection context.

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 full schema coverage, read-only annotations, and no output schema, this description is reasonably complete: it states the domain, the query scope, and the key result fields. It could be stronger by explicitly differentiating from the nearest FDA sibling tools, but it is not missing essential information for basic invocation.

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 has 100% description coverage for all six parameters, so the description does not need to repeat parameter details. It reinforces the core 'specific drug' concept and mentions reactions, which overlaps with the reaction parameter, but adds no substantive semantic value beyond the schema.

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 the resource as FAERS adverse event reports and explicitly says they are 'for a specific drug.' It also lists what each result contains (demographics, reactions, outcome, seriousness), which clearly distinguishes this tool from siblings like fda_drug_lookup and fda_drug_recalls.

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 phrase 'Used for pharmacovigilance and post-market safety analysis' gives a clear intended use context, but it does not state when to prefer this tool over related FDA tools such as fda_drug_lookup, fda_drug_recalls, or fda_food_recalls, nor does it provide any exclusions.

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