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 covered. The description adds the claim that an ingredient density input is accepted, which is useful context if true, but discloses nothing about precision, rounding, or how density is actually applied.

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 definition is short and front-loads the conversion scope, but several sentences are inaccurate or low-value: the placeholder 'Returns: {original}' conveys nothing, and the parameter list repeats wrong names. The trailing 'See list_bundles' pointer is tangential for a conversion tool.

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?

Safety is covered by annotations and an output schema exists, so return values need not be described. However, for a 3-required-param conversion tool the description omits decimal precision and density handling while asserting an ingredient parameter the schema does not accept, leaving the agent with a partly wrong mental model.

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 baseline would be 3, but the description actively misleads: it names inputs as 'value, from, to, ingredient' when the schema defines amount, from_unit, to_unit, and 'ingredient' does not exist at all. This is worse than staying silent and could cause a bad call.

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) plus resource (recipe quantities) and lists the unit families involved, and the 'Use for international recipe translation' clause distinguishes it from the many non-cooking converters in the sibling list. It does not, however, clearly separate it from close cousins like convert_cooking or calculate_baking_conversion.

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 international recipe translation' gives an implied context but no explicit when-not or alternative routing, even though near-identical siblings (convert_cooking, calculate_baking_conversion, calculate_recipe_scale) exist. The agent must guess which converter wins for a given request.

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