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

readOnlyHint=true already establishes a safe read, so the bar is lower; the description usefully adds that the result set is individual case reports tied to the openFDA drug/event endpoint. It says nothing about openFDA rate limits, result volume, or what a case report contains.

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?

Three short sentences, each earning its place: domain expansion, return granularity, and source endpoint. Nothing is repeated and no filler is present.

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?

For a no-required-parameter search tool with no output schema and full schema coverage, the description covers purpose, data source, and return form adequately. Minor gaps remain around result volume/rate limits, but the agent has enough to call it 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 description coverage is 100%, so the four parameters (skip, limit, sort, search) are fully documented in the schema itself, including Lucene syntax and pagination caps. The description adds no parameter-level meaning, which is acceptable given the schema does the heavy lifting.

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 named resource (FAERS adverse-event reports of drug side effects, reactions, medication errors), plus the underlying endpoint (openFDA drug/event). An agent can immediately separate this from search_drug_labels, search_drug_recalls, or search_device_events without opening any schema.

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 implied by the data domain but never stated: there is no guidance on when to choose this over siblings like count or openfda_query, nor any exclusion or prerequisite. The note that it 'Returns individual case reports' hints at the raw-record use case but does not route the agent explicitly.

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