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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context that this returns individual case reports rather than aggregates and that it maps to the openFDA drug/event endpoint, but says nothing about pagination limits, rate limits, or result ordering behavior.

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 action and dataset, no filler sentences, and short enough to scan quickly. The trailing 'openFDA drug/event endpoint.' fragment is slightly tacked-on but still informative.

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 output schema, the description correctly notes that individual case reports are returned, and pagination/query mechanics are fully documented in the schema. What is missing is usage context relative to sibling search tools, which would help an agent route correctly.

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 coverage is 100% with no required parameters, so the schema already documents skip, sort, limit, and the Lucene query syntax in detail. The description contributes nothing about parameter semantics beyond the dataset name. 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?

States a specific verb (Search) and a precisely scoped resource (FDA Adverse Event Reporting System reports of side effects, adverse reactions, medication errors), and names the underlying openFDA endpoint. This is clearly distinct from the sibling searches for labels, recalls, NDC, and Drugs@FDA.

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 explains what the dataset contains but gives no explicit when-to-use guidance, no prerequisites, and never names an alternative (e.g., search_drug_labels or search_drug_recalls) or the condition that would select one over this tool. Usage must be inferred from the name alone.

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