Get a brewery's beer list

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety is covered. The description adds useful behavioral context beyond annotations: it specifies the response content (per-beer rating, check-in counts) and that sorting and paging are supported. 'Read-only' is redundant with annotations but not contradictory.

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 short sentences, front-loaded with the core purpose, followed by supported features and a practical source for the required identifier. No wasted words or repetition beyond the redundant 'Read-only'.

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 read-only list tool with complete schema coverage and rich annotations, the description is sufficient. It tells the agent what data to expect, that pagination/sorting exists, and where to obtain a valid brewery_id. No essential calling information is missing.

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 schema already fully documents all five parameters including enums, defaults, and response-shape differences. The description only lightly re-mentions sorting and paging, adding no meaning beyond the schema.

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 and resource: 'Get the beers a brewery makes, by brewery id, with per-beer rating and check-in counts.' This clearly distinguishes the tool from brewery metadata tools like untappd_brewery_info and beer-specific tools like untappd_beer_info.

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?

Provides a clear prerequisite workflow: 'Get an id from untappd_search_brewery.' It also implies when to use the tool based on the brewery-id input, though it does not explicitly state when not to use it or compare it to sibling tools.

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