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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description's job is to add grounding context, which it does: it names the USDA FSIS source, the 325°F roasting range, the 165°F safe internal temperature, and the fact that supplying a serve time produces back-calculated start times. It does not describe output units or what happens outside the stated weight bounds, but the conditional-output behavior is valuable disclosure beyond 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 dense sentences: the first front-loads the usage trigger and coverage, the second delivers the return payload and the domain bounds. No filler, no repetition of the title, and the exclusions come last where they are easy to scan.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes them accurately. Combined with the explicit weight-range limits and domain exclusions, an agent has everything needed to decide to call this tool and to supply weight plus optional serve_time correctly.

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 the baseline is 3, and the description earns an increment by explaining the conditional effect of serve_time (clock times to start thawing and roasting) and the stuffed/unstuffed branch, which clarifies how parameters change results rather than just restating field docs. It does not mention clock, rest_minutes, or the default Thanksgiving date, leaving those entirely to the schema.

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 a specific verb and resource (calculate turkey roast and thaw times) and enumerates the exact input dimensions it handles: weight in lb or kg, stuffed vs unstuffed, fridge vs cold-water thaw. It also bounds the domain (4 to 24 lb, stuffed 8 to 24 lb), so an agent knows precisely what question this tool answers.

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?

It gives an explicit trigger condition ("Use this when the user asks a turkey cooking time calculator question") and explicit exclusions ("Does not cover other meats, deep frying or smoking"). The only minor gap is that it does not name the sibling plan_cooking_timeline for multi-dish planning, but the when/when-not framing is unambiguous for the tool's own domain.

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