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

Annotations already cover readOnly/idempotent/openWorld safety profile, so the bar is lower; the description nonetheless adds a genuinely important caveat that reports are spontaneous submissions and not validated causal or incidence data. It also discloses a non-obvious upstream behavior: brand names are resolved against the ingredient field. Return shape/pagination is not discussed, but limit is documented in schema.

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 purpose and examples, then the parameter note and the data-quality caveat. The three example questions are slightly verbose but serve to disambiguate intent; every sentence carries information.

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 7-param, no-output-schema search tool this is close to complete: purpose, source, species scope, parameter aliasing, and a data-reliability caveat are all present. Missing only minor hints on result volume or ordering beyond the limit parameter.

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%, so baseline is 3; the description adds real value by explaining that 'drug' brand names are resolved against the ingredient field because product names are recorded there upstream, which is semantics the schema does not convey. It does not add format detail for since/limit/reaction 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?

Specific verb+resource (search FDA CVM adverse event reports) with explicit scope (veterinary drugs and parasite preventives; dogs, cats, horses, cattle) and concrete example queries that pin down what it answers. It is clearly distinguishable from siblings vet_adverse_event_summary and vet_product_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?

Gives natural-language use cases and clarifies the drug vs active_ingredient choice, noting either works. It stops short of explicitly routing the agent away from sibling tools like vet_adverse_event_summary or vet_product_recalls, so sibling differentiation is implied rather than stated.

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