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 description's job is to add behavior beyond that, which it does: it discloses the per-method return shapes (day band on fridge, hour band on cold water) and the 30-minutes-per-pound rule. It stops short of disclosing out-of-range handling for weights outside 8-24 lb.

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?

The core facts are front-loaded after a one-line framing sentence about Thanksgiving risk, and the method-specific behavior follows in a single compact sentence. The opening hook costs a little space but is short and does orient the reader quickly.

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 must characterize the return value, and it does so for both methods plus the conditional start date. Annotations and the fully documented four-parameter schema cover safety and inputs, leaving only edge-case behavior (invalid weights, date formats) unaddressed.

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 one step above it by adding the quantitative thaw rate (30 minutes per pound) and by clarifying the differing meaning of the result depending on method. The cook_time framing distinction itself lives in the schema, so no additional credit is due there.

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 names the exact resource and computed quantity ('How long a turkey takes to thaw'), and specifies the two USDA methods and the 8-24 lb range, so the agent knows precisely what comes back. It never explicitly distinguishes itself from get_roast_time or plan_turkey_timeline, so sibling differentiation is only implicit through the cook_time reference.

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 rather than stated: the description explains that a fridge thaw yields a chart band in days and a start date when a cook date is supplied, and that cold water yields a band in hours. It never says when to reach for this tool versus plan_turkey_timeline (which also produces a timeline) or when the tool is the wrong choice.

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