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

Annotations already declare readOnly/non-destructive/openWorld, so safety is covered. The description adds genuine behavioral value by disclosing the return enrichment ('Results note how many of the main liquors you already own') and the fact that optional fields are best-effort hints ('when known'). It stops short of describing limit/pagination behavior, so not a 5.

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 tight sentences, front-loaded with the core purpose, then parameter guidance, then the alternative. No filler and every sentence carries 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?

For a 5-param, no-output-schema tool, the description covers purpose, the return shape, and the sibling routing well. The only meaningful gap is the undocumented limit parameter, which keeps it from being fully 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?

Schema coverage is only 40%, so the description must compensate and it partially does: it clarifies bottleName is the bottle's display name and that spiritType/category/proof are optional refinements ('when known'). The limit parameter is left unexplained in both schema and description, and no format guidance is added for proof.

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?

States a specific verb+resource ('cocktails to make with a bottle') and anchors it to a familiar UI concept (the recipe rail on a bottle page), so the agent knows exactly what this returns.

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?

Explicitly routes browsing traffic elsewhere ('For browsing all drinks use explore_recipes'), and names the trigger condition for this tool (you have a specific bottle). The alternative and the selecting condition are both stated.

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