calculate_pet_bmi

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

With no annotations, the description should disclose behavioral traits. It states it 'estimates' and 'returns thresholds', implying a read-only calculation. However, it does not explicitly confirm no side effects or authentication needs. For a simple calculator, this is adequate but not comprehensive.

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 sentences, front-loaded with purpose and return value. Efficient with no wasted words, but could add a bit more detail without harming conciseness.

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 simplicity of the tool and existence of an output schema (which may explain return values), the description is partially complete. It lacks clarity on the 'thresholds' return format and does not specify precision or measurement guidelines. Adequate for a basic tool but not fully informative.

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 0%, but the description does not explain any parameters beyond implying 'animal' relates to dogs/cats. The numerical parameters (weight_kg, body_length_cm) are not described in terms of meaning, typical ranges, or measurement methods. This is insufficient compensation for the lack of schema descriptions.

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 estimates a body condition score proxy (BMI) for dogs and cats, using a specific verb ('estimate') and resource ('BMI for pets'). It distinguishes from siblings by specifying the animal types and pointing to related 'animaux' calculators.

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?

No explicit guidance on when to use this tool versus alternatives like calculate_pet_age or calculate_pet_food_portion. The mention of 'list_bundles' implies related tools but does not provide selection criteria.

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