calculate_recipe_scale

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

No annotations provided, so description carries full burden. Only states 'Returns adjusted quantities,' omitting any safety guarantees, edge cases, or whether the operation is idempotent. For a simple calculator, this is minimal transparency.

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?

Description is short but contains minor redundancy ('Scale...' and 'Use for adjusting recipes' say similar things). Front-loads the main action, but could be tighter without losing meaning.

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?

Despite an output schema existing, the description fails to clarify that it handles one ingredient at a time (implied by the single 'amount' parameter). Lacks explanation of the scaling factor or constraints like positive numbers, making it incomplete for a calculator with 3 numeric inputs.

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 has 100% coverage with descriptions for all three parameters. However, the description misrepresents inputs by mentioning 'ingredients with quantities' (plural) while schema has only a single 'amount' parameter. This conflict reduces clarity and adds confusion beyond what the schema provides.

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?

Clearly states the tool scales recipe quantities to a new servings count, which is a specific verb+resource. However, it does not differentiate from sibling tool 'calculate_recipe_scaling' or explicitly mention that it handles a single ingredient per call.

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?

Says 'Use for adjusting recipes,' providing a use case but no explicit guidance on when not to use or alternatives. References list_bundles for related calculators, but lacks clear differentiation.

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