Search Untappd beers

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

Annotations already declare readOnlyHint and idempotentHint; the description confirms read-only and adds that results are ranked matches. However, the description claims the response includes global rating, while the view parameter's default compact projection omits that field — only 'full' includes it. This slight inconsistency makes the behavioral claim less reliable.

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 concise sentences with the core purpose front-loaded, a useful alternative hint, and a one-word behavioral tag. No filler or repetition of schema details.

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?

The description, together with a 100%-covered schema and detailed view explanations, covers search scope, sorting, paging, and output shape. The main gaps are the rating inconsistency and the lack of an explicit pointer to the brewery-search sibling, but these are minor given the clear sibling names and schema.

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% and the schema already explains sort, view, limit, offset, and query. The description contributes extra query-format guidance ('Brewery Beer') and summarizes the returned fields, going beyond the baseline without duplicating 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: search Untappd for beers by name, optionally in 'Brewery Beer' format. It lists the returned fields and explicitly routes to untappd_beer_info for full detail, clearly distinguishing it from the untappd_search_brewerry sibling.

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?

Gives a clear context: use when you need to find beers by name, and it points elsewhere (untappd_beer_info) once you have a bid. It does not explicitly state when not to use it or name untappd_search_brewerry as the alternative for brewery searches, so it stops short of perfect routing guidance.

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