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

With no annotations, the description must fully disclose behavior. It correctly states that the tool computes units and grams, but omits any details about side effects, permissions, or limitations. For a simple calculator, this is adequate but not detailed.

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 extremely concise with two sentences that front-load the core purpose. Every sentence adds value without redundancy.

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?

For a straightforward calculation tool with an output schema available, the description covers the essentials: what it computes, when to use it, and the inputs. It could be slightly more complete by mentioning that multiple drinks can be analyzed, but it is largely sufficient.

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 'Inputs: volume mL, ABV %' but does not explain the array structure, the 'type' field, or that multiple drinks can be input simultaneously. This insufficiently fills the gap left by missing schema descriptions.

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 UK alcohol units and grams of pure alcohol for health tracking and limit awareness. It distinguishes from sibling tools by specifying 'UK units' and mentioning 'standard-drink equivalent', but does not explicitly differentiate from other alcohol-related calculators like calculate_blood_alcohol.

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 says 'Use for health tracking and limit awareness,' which provides some usage context. It mentions a related tool group (list_bundles for cuisine calculators) but does not specify when not to use this tool or name alternatives for similar calculations, leaving gaps in guidance.

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