calculate_grocery_unit_comparison

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

With no annotations, the description bears full burden. It discloses unit normalization behavior (g→kg, mL/cL→L) and output structure ({best_value, savings_vs_priciest}). It is transparent but does not cover error handling or unsupported units.

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 wasted words. The structure is front-loaded with purpose and behavior, followed by output and a pointer to related tools.

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 description covers purpose, normalization, and return format adequately for a simple tool. It references list_bundles for related calculators. Missing explicit constraints on units (though schema covers it) but overall complete.

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?

The input schema has 100% coverage with description for items. The tool description does not add new meaning beyond the schema, so the baseline of 3 is appropriate.

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 compares unit prices of grocery items, normalizes units (g→kg, mL/cL→L), and returns best_value and savings_vs_priciest. It uses a specific verb (compare) and resource (unit prices), making the purpose distinct among siblings.

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 implies usage for grocery item price comparison and mentions a related tool (list_bundles). However, it lacks explicit guidance on when not to use this tool or direct alternatives across the many calculator tools.

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