calculate_freezer_duration

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the function (returning duration) but does not mention what the tool does not do (e.g., no data modification, no authentication needs, no rate limits). The behavior is minimally transparent.

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?

Two sentences with no superfluous information. The first sentence states the core purpose, and the second directs to related tools. Efficient and to the point.

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 (single enum parameter, output schema exists), the description covers the essential purpose and hints at related tools. It does not explain the output format, but the output schema likely handles that. For a straightforward lookup tool, this is adequate.

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 0%, so the description should add meaning beyond the enum values. However, the description does not explain what each food_type means or how the duration is returned (e.g., in days, weeks). The enum values are self-explanatory, but the description fails to provide any additional context about the 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 returns the maximum recommended freezer storage duration for a given food type. It uses a specific verb ('Return') and resource, distinguishing its purpose. However, it does not explicitly differentiate from the many sibling calculator tools, such as calculate_meat_cooking or calculate_cat_food, which are also food-related.

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 provides no guidance on when to use this tool versus alternatives. It only mentions 'See list_bundles for related cuisine calculators,' which is a weak hint and does not specify exclusions or conditions for use.

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