find_animals

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

No annotations are provided, so the description must disclose behavior. It mentions the return envelope but does not state that the operation is read-only, whether it requires special permissions, or any side effects. For a search tool, this is minimal transparency.

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 sentences: the first states the purpose with specific criteria, the second describes the return format. No unnecessary words or redundancy.

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?

Given the presence of an output schema, the description is not required to detail return values. However, it covers only 3 of 5 parameters, omitting pagination details and any search behavior specifics (e.g., case sensitivity, partial matching). Completeness is adequate but has clear gaps.

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 description adds meaning by listing searchable attributes (name, species, breed) which correspond to parameters 'name', 'species_id', 'breed_id'. However, it does not explain pagination parameters ('page', 'limit') and the terms 'species' and 'breed' are ambiguous (text vs. ID). With 0% schema coverage, the description partially compensates but not fully.

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 verb 'search' and the resource 'animals', and specifies searchable attributes (name, species, breed). However, it does not explicitly differentiate from sibling tools like 'get_animal' or 'find_appointments', making it slightly less clear for exact purpose boundaries.

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 implies usage context through the search criteria, but lacks explicit guidance on when to use this tool versus alternatives. No 'when not to use' or alternative tool references are provided.

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