calculate_ideal_weight_range

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

With no annotations, the description partially covers behavior: it explains the BMI-based calculation and return format. However, it omits that sex and frame are required inputs, and does not disclose side effects, permissions, or rate limits.

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 three sentences, concise and front-loaded with the main purpose. Every sentence adds value without 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?

The description covers the return format and method, but lacks explanation of the sex and frame parameters. Despite a simple tool, the incomplete input description slightly reduces 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?

Schema coverage is 100%, but the description misleadingly only mentions 'height cm' while ignoring required parameters sex and frame. The added BMI range context is helpful but does not fully compensate for the omission.

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?

Description clearly states the tool computes a healthy weight range using BMI 18.5-24.9, suitable for nutrition planning. It distinguishes from other calculate tools by specifying the output (range in kg and lb) and references related calculators via list_bundles.

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 says 'Use for nutrition planning' but does not clearly differentiate from sibling tools like calculate_ideal_weight or provide when-not-to-use scenarios. No explicit alternatives are mentioned beyond a vague reference to 'sante' calculators.

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