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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds nothing behavioral beyond the content list — no output shape, no units (Celsius/Fahrenheit, fan/gas), no note on whether times are per-weight or fixed.

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?

One front-loaded sentence that leads with the deliverable (times and temperatures) before enumerating coverage. The long item list is informative rather than padding, though it could be tightened with grouping.

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 one-optional-parameter reference lookup with no output schema, the description covers scope adequately. It is thin on what the returned values look like (units, per-item rows), which matters for a data-lookup tool.

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% and the single optional 'query' parameter is already documented with examples that mirror the food list. The description adds no filtering semantics beyond what the schema states, so baseline 3 applies.

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 a concrete resource set — cooking times and oven temperatures for potatoes, Yorkshire puddings and chicken pieces — so an agent knows exactly what data it returns. The enumerated items implicitly separate it from roast_cooking_time and turkey_cooking_time, though no sibling is named explicitly.

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 only implied by the covered-food list; there is no explicit statement of when to call this versus roast_cooking_time or plan_roast_dinner. An agent can infer the boundary from the item list, but must do the work itself.

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