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

The readOnlyHint=true annotation already establishes this is a safe read, so the description only needs to add context — and it does add the data source and endpoint identity. It says nothing about pagination ceilings, result caps, or rate limiting, which are left to the schema's skip/limit descriptions.

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?

Two tight sentences, zero filler, with the dataset identity front-loaded and the endpoint reference appended as a clarifying pointer. Nothing repeats the title or the annotations.

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 four-optional-parameter search wrapper with fully documented schema and a readOnly annotation, the description supplies enough to select and invoke it correctly; the lack of an output schema is not a gap since search results are self-describing. Only the missing sibling routing keeps it short of full completeness.

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%: skip, sort, limit and the Lucene 'search' syntax are all documented in the schema, including ranges, .exact phrases and date formats. The description adds no parameter detail beyond what the schema already supplies, 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 names a specific verb (Search) and a precisely bounded resource: the CFSAN Adverse Event Reporting System covering foods, dietary supplements and cosmetics. It even names the backing endpoint ('openFDA food/event'), which distinguishes it from its nearest sibling search_food_recalls, which covers recalls rather than adverse events.

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 when-to-use or when-not-to-use guidance and no routing to alternatives such as search_food_recalls, count or openfda_query. The agent must infer from the dataset name alone that this is the adverse-event dataset rather than the recall dataset.

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