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

Beyond annotations that already establish a safe read-only lookup, the description adds meaningful behavior: it returns a chart band plus a middle-of-band plan, computes oven-in time when dinner date/time are supplied, uses a different from-frozen chart, and notes frozen cooking takes at least 50 percent longer. It still does not fully specify the exact response shape, which matters because 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?

The description is relatively compact and organized around the roast-time behavior, frozen variant, weight range, and final safety check. The opening dinner-time framing is somewhat rhetorical, but it sets context rather than adding unnecessary detail.

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 four-parameter, read-only lookup with rich schema coverage and annotations, the description covers the important cooking context, frozen behavior, weight bounds, and the 165F safety rule. The main remaining gap is that return-value structure is not spelled out and sibling routing is not explicit.

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%, so the schema already carries parameter meaning, including the 8 to 24 lb weight range, default thawed state, and dinner date/time behavior. The description reinforces some of this and adds the chart-band framing, but most parameter semantics are already present in 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 precise resource and scope: USDA roast-time guidance for unstuffed turkey at 325F, 8 to 24 lb, with a separate frozen path. It does not explicitly distinguish itself from get_thaw_time or plan_turkey_timeline, so the sibling differentiation is only implicit in the roast/oven-time framing.

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 explains that dinner date and time cause the tool to return oven-in time, and that state=frozen switches to the from-frozen chart. However, it does not explicitly say when to use this tool instead of get_thaw_time or plan_turkey_timeline, leaving alternative selection implied.

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