get_veterinary_species

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

No annotations are provided, so the description carries the burden. It discloses the domain restriction (veterinary only) and the semantic output (approved species), which is meaningful for a simple read-only lookup. It doesn't address edge cases like invalid codes, but that is acceptable for this tool type.

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 concise, front-loaded sentences that state the action and result with no redundancy or filler.

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 simple lookup with full schema coverage and an existing output schema, the description is complete. It could mention behavior for non-veterinary codes or empty results, but these are not critical given the tool's straightforward nature.

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 input schema has 100% parameter description coverage with clear definitions for drug_code, lang, and type. The tool description adds little beyond the drug product context, so baseline 3 is appropriate.

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 action ('Get'), the specific resource ('veterinary species for a veterinary drug product'), and the return value ('animal species the drug is approved for'), distinguishing it from sibling drug lookup tools.

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?

Provides an explicit scope constraint ('Only applicable to veterinary drugs') that tells the agent when this tool is appropriate. It doesn't name alternative tools for non-veterinary drugs, but the exclusion is clear.

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