calculate_meat_cooking_time

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

No annotations are provided, so the description carries full burden. It states that the tool returns time in minutes and oven temperature in °C, but does not disclose whether it is read-only, any side effects, or permissions needed. For a calculator tool, this is adequate but not rich.

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 two sentences, front-loaded with the core purpose, and includes input/output and a reference to related tools. Every sentence adds value with no wasted words.

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?

Given the existence of an output schema, the description does not need to detail return values, but it does. It covers inputs and outputs and hints at related tools. However, it could be more complete by differentiating from similar sibling tools.

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 baseline is 3. The description repeats parameter names (meat type, weight kg, target doneness) without adding new meaning. The mention of 'cut' is ambiguous and does not correspond to any parameter.

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 clearly states it computes oven cooking time for meat by cut, weight, and doneness. It specifies inputs and returns, but does not explicitly differentiate from similar siblings like calculate_cooking_time or calculate_meat_cooking.

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?

The description only says 'Use for cooking,' which is vague. It does not specify when to use this tool versus alternatives, nor does it provide explicit when-not or exclusion criteria. The mention of list_bundles is insufficient guidance.

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