calculate_cooking_time

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

No annotations provided, so description carries full burden. It mentions return values (time min and target internal temp) but lacks details on side effects, rate limits, or other behavioral traits. Adequate but not comprehensive.

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?

Three sentences, front-loaded with core purpose. Efficient, though second sentence could be combined with first. No extraneous information.

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 tool's simplicity, description covers inputs and outputs adequately. However, the missing doneness parameter and method mismatch reduce completeness. Output schema presence partially compensates.

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?

Description adds meaning but contains inaccuracies: mentions 'doneness' parameter which is absent from schema, and says 'weight g' while schema uses 'weight_kg'. With 0% schema coverage, description must be precise. These mismatches could mislead an agent.

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?

Description clearly states it estimates cooking time for specific foods based on weight, method, and doneness. Purpose is specific, but does not distinguish from sibling tools like 'calculate_meat_cooking' and 'calculate_meat_cooking_time'.

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?

States 'Use for kitchen planning' and references list_bundles for related calculators, but does not provide explicit when-to-use or when-not-to-use guidance or direct alternatives.

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