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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and purity are covered. The description adds real behavioral value beyond that: the actual thawing rates (12 hours per kg refrigerated, 30 minutes per lb in water) and the fact that supplying cook_date yields a back-planned freezer-to-fridge day rather than a bare duration.

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 sentence with the core answer (thawing duration) front-loaded and the method rates and cook-date behavior following as qualifying clauses. No filler, no repetition of the title.

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 closed-world calculator with a fully described four-parameter schema, complete annotations, and no output schema, the description supplies everything needed to choose parameters and anticipate the result. Nothing material 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 all four parameters are already documented, setting a baseline of 3. The description still adds meaning by attaching each rate to a specific method, making clear why the fridge vs water enum matters for the result, which the schema alone does not convey.

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 resource (thawing time for a frozen turkey) with concrete rates for two methods, plus the second capability of picking a freezer-to-fridge day from a cook date. This is clearly separable from turkey_cooking_time and roast_cooking_time, which concern cooking rather than thawing.

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 by the parenthetical method notes (fridge vs cold water) and by the optional cook_date, but the description never explicitly says when to use this versus turkey_cooking_time or plan_roast_dinner, nor does it state prerequisites or exclusions.

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