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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds value the annotations cannot: it discloses the substantive outputs the agent will receive, including USDA roasting guidance at a specific temperature and both thawing methods, which is important since no output schema exists.

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?

A single compact sentence with zero filler, and the primary output (turkey size) is front-loaded ahead of the secondary timings. It reads as a noun-phrase list rather than a complete sentence, which is slightly less self-explanatory but costs no tokens.

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?

With no output schema, the description correctly carries the return-value burden by naming all four computed results. For a read-only, idempotent calculator with fully documented parameters and no side effects, nothing critical is missing, though it could note that results assume standard USDA guidance.

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 100%, with enums and even a default ('Default whole') documented inline, so the schema does the heavy lifting. The description only echoes 'guest count' and adds no interpretation of how 'stuffed', 'kind', or 'appetite' change the computed result beyond what the schema already states.

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 enumerates exactly what the tool computes: turkey size for a guest count, USDA roasting time at 325°F, fridge and cold-water thawing times, and done temperature. That is specific and unambiguous, though it never distinguishes itself from siblings like ham_calculator or prime_rib_calculator, relying on the name alone to convey the protein.

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 phrase 'for a guest count' implies the planning scenario, so usage is inferable. But there is no explicit when-to-use statement, no mention of the stuffing/appetite options as decision drivers, and no routing to alternatives such as prime_rib_calculator or thanksgiving_timeline for related planning tasks.

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