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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds that results come from USDA FSIS and include cooking/reheating time and safe temperature, which is real added context. It says nothing about how quantity scales with the appetite parameter or how the label/cut constraint manifests (error vs. adjusted result).

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?

Front-loaded with the outcome, then a compact glossary of label values and a one-clause caveat. Fragment style is dense but readable; no sentence is wasted, though the label glossary could be formatted more scannably.

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?

No output schema exists, so the description correctly states what comes back: per-person quantity, cooking/reheating time, and safe temperature. For a 5-parameter calculator the main remaining gap is the unexplained appetite and cut semantics and how an unsupported label/cut pair is handled.

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?

With only 40% schema coverage, the description does heavy lifting by defining all four 'label' enum values (cooked/cbe/fresh/country) and flagging that cut availability varies by label. It leaves 'cut' (spiral/whole/half/boneless) and 'appetite' (dinner/leftovers) undefined, relying on intuition.

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 opening sentence names a specific verb+resource: per-person ham purchase quantity plus USDA FSIS cooking/reheating time and safe temperature. It's clearly distinct in resource from siblings like turkey_calculator and prime_rib_calculator, though it never names an alternative explicitly.

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?

Usage is implied (meal planning for a ham) with a useful constraint caveat, 'Not every label has every cut,' which warns about invalid combinations. There is no explicit when-to-use vs. another calculator, and no guidance on when to pick this over party_food_calculator.

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