calculate_food_cost_per_serving

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 what the tool returns (cost per serving and total) but lacks details on edge cases, prerequisites, or limitations. The input schema constraints are not elaborated.

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 concise with two sentences: first outlines purpose, second adds usage context and helpful sibling reference. 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?

The tool has an output schema (not shown) and the description mentions return values. However, it does not explain the ingredient object structure or handle edge cases, making it adequate but not thorough for a simple calculator.

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 must compensate. It mentions 'list of ingredients with cost and quantity used, servings' but fails to detail the structure of the ingredients array (e.g., fields like name, price, total_quantity). This provides only marginal improvement over parameter names.

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 the tool computes food cost per serving from ingredient lists, with a specific verb ('compute') and resource ('food cost per serving'). It distinguishes from sibling 'cuisine' calculators by referencing list_bundles.

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 context for use ('restaurants, meal-prep services') and directs to list_bundles for related calculators. However, it does not explicitly state when not to use this tool or exclude alternatives.

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