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

The annotations already disclose that this is a read-only, idempotent, non-destructive, closed-world calculation. The description adds little behavioral context beyond 'Returns converted quantity,' which is redundant because an output schema exists, and it omits any ingredient-specific conversion assumptions or limitations.

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 and front-loads the purpose, but one sentence lists incorrect parameters and another cross-references list_bundles for unrelated 'cuisine' calculators, which does not earn its place. The overall size is reasonable, but the content includes low-value and inaccurate material.

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 the simple two-parameter schema, 0% schema description coverage, and an output schema that already covers the return value, the description should at least explain ingredient and quantity_cups. Instead it misstates the inputs and provides no conversion basis, so it is not complete enough for correct invocation.

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 description coverage is 0% and the actual schema has only two parameters: ingredient and quantity_cups. The description instead lists 'value, from-unit, to-unit,' which do not exist in the schema, and it omits quantity_cups entirely, making its parameter guidance actively misleading.

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 a clear verb and resource: converting baking measurements between cups, tablespoons, grams, and milliliters for common ingredients. It adds a usage context, 'translating recipes across regions,' but does not explicitly distinguish itself from close siblings such as calculate_cooking_conversion or convert_cooking.

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?

It gives an implied usage context ('Use for translating recipes across regions') but does not state when to choose this tool over the many other conversion and cooking calculators. There are no exclusions or explicit alternatives named.

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