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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered externally. The description adds only 'Returns: {input}', a cryptic placeholder that conveys little, so it adds minimal behavioral context beyond the annotations.

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 purpose sentence is front-loaded and efficient, but 'Returns: {input}' is a wasted, unhelpful fragment given a full output schema exists, and the trailing 'See list_bundles' sentence is tangential.

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?

An output schema is present so return values need not be explained, and annotations cover safety. The remaining gaps are the unit/enum mismatch and the absence of guidance against the numerous near-identical conversion siblings, leaving the agent to guess among them.

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%, so the schema already documents all three parameters, but the description's unit list ('ml, L, g, kg, cup, tbsp, tsp, fl_oz, oz') contradicts the schema enum (cup, tbsp, tsp, ml, fl_oz, l): g, kg, and oz are not valid values. This misleading enumeration actively undermines the otherwise complete schema.

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?

States a specific verb 'Convert' and a specific resource 'cooking measurements', and enumerates the units, which distinguishes it from the generic convert_volume sibling. It does not, however, differentiate itself from the very close sibling calculate_cooking_conversion or explain why both exist.

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?

'Use for recipe scaling and translating' gives a use case, but there is no when-not guidance and no named alternative among the many conversion siblings (calculate_baking_conversion, convert_volume, calculate_recipe_scale). The 'See list_bundles' pointer is a weak, indirect hint rather than routing guidance.

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