calculate_baking_conversion

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

No annotations provided, and the description lists inputs ('value, from-unit, to-unit') that don't exist in the schema, creating mismatch. No disclosure of behavioral traits like supported units or output format.

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 but contains inaccurate information, making it inefficient. Key details are missing, and the input list is misleading.

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?

Fails to explain actual usage (only cups input, enum ingredients, output unit). No output schema provided, and the description omits critical context for a tool with this complexity.

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 parameters (ingredient, quantity_cups) are not explained; instead, nonexistent parameters are mentioned. With 0% schema coverage, the description adds no meaningful guidance and actively misleads.

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 'convert baking measurements' but the input schema only accepts 'quantity_cups', contradicting the claim of converting from any unit. This vagueness fails to accurately represent the tool's scope.

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 suggests using for recipe translation and references 'list_bundles', but does not differentiate from siblings like 'convert_cooking' or 'calculate_cooking_conversion'.

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