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

Annotations already disclose read-only and idempotent behavior. The description adds that it returns event reports with animal details, drug information, and adverse reactions, which is useful. However, it also mentions 'reaction' as a filterable criterion, but no such parameter exists in the schema, creating potential confusion about actual capabilities. This partial inaccuracy lowers the score.

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 two sentences, front-loaded with the primary action, quickly summarizes return contents, and appropriately references a related tool. No wasted words.

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 search tool with 7 parameters and no output schema, the description gives a broad overview of filters and return contents, which is decent. However, it omits that 'reaction' is not a supported filter, and it does not mention default limit or pagination behavior (though these are in the schema). The misleading 'reaction' mention creates a gap in 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?

The schema provides 100% coverage of parameters with descriptions. The description adds a high-level grouping of filter types (species, drug name, serious flag, date range) but introduces a 'reaction' filter that is not present in the schema, diminishing its value. Baseline is 3 because schema already 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?

The description clearly states the tool's function: 'Search veterinary adverse events (animal drug safety reports)' with a specific verb and resource. It enumerates the main filter categories and explicitly distinguishes itself from the related sibling fda_search_aphis, making its purpose unambiguous.

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 provides clear context on what the tool searches for (species, drug name, serious flag, date range) and mentions a related tool for veterinary biologics facilities, implying when to choose this tool over that alternative. However, it stops short of an explicit 'use this when you need X' or 'do not use for Y' statement.

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