Get Untappd brewery detail

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

Annotations already provide readOnlyHint, idempotentHint, and openWorldHint, so the description need not repeat those. The description adds value by stating 'Read-only' and listing the returned fields, but it does not disclose any additional behavioral traits (e.g., rate limits, authentication needs). No contradictions with 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?

Two sentences, front-loaded with the core purpose, and no wasted words. Every sentence adds value: first states the tool's function and output, second explains how to get the required input. Perfectly concise.

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?

Without an output schema, the description compensates by listing the key return fields (description, location, type, rating, total check-ins, popular beers). It also connects to the search tool. Could mention potential limitations (e.g., number of popular beers), but overall it is sufficient for an agent to use correctly.

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 100% with descriptions for both parameters: brewery_id and compact. The description does not add significant meaning beyond the schema—it implies the default is full detail, but that is already clear from the schema description of compact. Baseline 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 action ('Get full detail') and the resource ('brewery by its Untappd brewery id'), and lists the specific data returned (description, location, type, rating, total check-ins, popular beers). It also distinguishes from sibling tools like untappd_search_brewery by explaining how to obtain the id.

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 explicit context for usage: obtain the brewery id from untappd_search_brewery. It clearly indicates the tool is read-only. While it does not explicitly state when not to use it, the context is sufficient, and the sibling tool list provides alternatives.

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