calculate_waist_hip_ratio

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

No annotations provided, but description doesn't disclose side effects or confirm that it's a pure read-only calculation. However, it is a calculator so behavior is implied. Still, more transparency about what it does not modify would be better.

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?

Extremely concise with two sentences; the first conveys core purpose, the second provides cross-reference. No redundant information.

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 no output schema, description briefly mentions return fields (risk_threshold, cardiovascular_risk). For a simple calculator with 3 parameters, this is sufficiently complete. Could have explained risk levels, but not necessary.

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% and parameters are well-documented. Description does not add extra meaning beyond the schema, so baseline score of 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?

Description clearly states the tool calculates waist-to-hip ratio and cardiovascular risk level, specifying the return fields. It distinguishes from sibling tools by referencing 'sante' 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?

Description provides minimal guidance, only suggesting to see list_bundles for related calculators. No explicit when or when-not to use, or alternative criteria.

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