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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is low. The description adds genuine behavioral substance beyond that: the prep quantity formula, the floor at zero, and the grouping-by-station output structure — none of which are stated in 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?

Two sentences, front-loaded with the outcome, with no filler. It is slightly dense with parentheticals but every clause carries real information; only minor tightening is possible.

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?

For a read-only, non-destructive tool with a full output schema and 100% parameter coverage, the description supplies the one thing structured fields cannot: the calculation rule and grouping behavior. Nothing an agent needs to call this correctly is missing.

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 is 3. The description earns above baseline by explaining the semantics behind the fields — par as 'the amount you want ready for service', on_hand as the counterpart, and the derived prep quantity that no schema field defines.

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+resource ('Build a kitchen prep list from par levels') and the exact computation involved. It does not explicitly contrast with the closest sibling get_recipe_prep_sheet, so sibling differentiation is left implicit rather than stated.

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 par-level framing implies when the tool applies (you have par levels and on-hand counts to reconcile), but there is no explicit when-to-use/when-not guidance and no mention of get_recipe_prep_sheet as the alternative for a recipe-derived sheet. Usage is inferable but not directed.

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