Get a brewery's beer list

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

Description adds 'Read-only' and mentions per-beer rating and check-in counts as behavioral traits. Annotations already declare readOnlyHint, idempotentHint, and openWorldHint; description enriches without contradiction.

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 only: first covers purpose and key outputs, second gives prerequisite. No wasted words, front-loaded with critical 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 list endpoint with no output schema, description covers purpose, required parameter source, parameter behaviors, and safety. Mentions output fields (rating, check-in counts). Lacks paging metadata details but overall sufficient.

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% and includes descriptions for all four parameters. The description briefly references sorting and paging but does not add significant meaning beyond the schema. 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?

Clearly states 'Get the beers a brewery makes' with specific verb and resource, includes output details (per-beer rating, check-in counts), and distinguishes from siblings like untappd_brewery_info or untappd_beer_info by focusing on the list.

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 says 'Get an id from untappd_search_brewery' to obtain the required brewery_id, and notes 'Read-only' to indicate safe usage. Does not explicitly list alternatives among siblings, but context is clear.

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