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

Annotations already declare readOnly, non-destructive, and idempotent, reducing the description's burden. The description adds a brief note about return structure, but it does not disclose any additional behavioral traits (e.g., randomness not being reproducible, absence of filtering). This is adequate but not rich.

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 a single, front-loaded sentence with no filler. It immediately states the action and then lists the key output details, earning every word.

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 simplicity (no params), rich annotations, and presence of an output schema, the description covers the essentials. It could mention how randomness works or explicitly contrast with get_cocktail, but it is largely complete for this low-complexity tool.

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 tool has zero parameters, so the description is not burdened with explaining inputs. Baseline for 0 params is 4, and the description appropriately focuses on the return value.

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 action ('Get') and resource ('random cocktail recipe'), and explicitly lists the return contents (ingredients, measurements, instructions, glassware, garnish). The word 'random' distinguishes it from sibling tools like search_cocktails and get_cocktail, which imply specific lookups.

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 the many cocktail-related siblings (e.g., get_cocktail, search_cocktails, cocktails_by_ingredient). No explicit or implicit hints about when 'random' is preferred over a targeted search.

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