calculate_ideal_weight_range

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

No annotations are provided, so the description must carry full transparency. It fails to mention that sex and frame inputs affect the calculation, and it does not describe what happens with invalid inputs or edge cases.

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 short with three sentences, but it omits critical parameter information. It includes a useful reference to list_bundles. Overall, it is not fully efficient due to missing details.

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 tool has 3 required parameters with enums, but the description does not explain how sex and frame affect the weight range. It only partially describes the output. An output schema exists but is not provided.

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?

Although input schema coverage is 100%, the description only mentions 'height cm' as input, omitting the required 'sex' and 'frame' parameters. This misleads the agent and reduces clarity.

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 states 'Compute healthy weight range based on BMI 18.5-24.9' and mentions nutrition planning, clearly indicating the tool's purpose. However, it does not distinguish itself from similar sibling tools like calculate_ideal_weight or calculate_bmi.

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 only gives a vague 'Use for nutrition planning' and lacks guidance on when to use this tool versus alternatives like calculate_ideal_weight for a single weight or calculate_bmi for BMI.

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