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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, and the description adds genuine context beyond them: exact-match folding rules, the success shape (found + recipe), the failure shape (found false, recipe null, browse_url), and that no credentials or payment are required. This is rich behavioral disclosure that complements rather than repeats the annotations.

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?

Front-loaded with purpose and scope, then match semantics, then success/failure shape, then auth. It is dense but nearly every sentence carries routing or contract information; the x402/licence aside is useful but slightly leans into explaining a sibling endpoint rather than this tool.

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 single-param read tool with annotations already covering safety and an output schema present, the description supplies everything an agent needs: exact-match semantics, success and failure contracts, and confirmation that no credentials or payment are involved. Nothing material is left unspecified.

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 100%, so the baseline is 3, but the description contextualizes the single 'name' parameter by restating the folding semantics (case, accents, punctuation) and the negative constraints in the context of matching against published records. It edges above baseline by framing what the match operates on, though it largely echoes the schema's own param text.

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 opens with a specific verb and resource ('Read one published cocktail recipe by name or slug') and ties the returned fields to the public page at /cocktails/<slug>. It explicitly distinguishes itself from drinkedin_list_data_products and GET /api/data/v1/cocktails, so an agent can route correctly without opening another schema.

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?

Usage boundaries are stated exhaustively: exact match on published name or slug, explicitly 'not a prefix, an ingredient search, or a list,' and it names the sibling (list_data_products) and endpoint (GET /api/data/v1/cocktails) that would otherwise be confused with it, including the credential/payment condition for the latter.

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