Get Untappd distinct beers

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

Annotations already provide readOnlyHint=true and idempotentHint=true. The description adds valuable context: 'Supports sorting and paging' and specifies that results include 'rating and check-in count per beer.' This goes beyond what annotations convey, but does not detail all behavioral aspects like rate limits.

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?

The description is three sentences: purpose, capabilities, and usage hint. It is front-loaded with the core function and wastes no words. However, it could be slightly tighter by merging the last two sentences, but still very efficient.

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?

There is no output schema, so the description should compensate by describing the return format more thoroughly. It mentions 'rating and check-in count per beer,' which gives some insight, but lacks details on pagination response structure, error handling, or how the compact parameter affects output. Partially complete.

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%, so baseline is 3. The description adds meaning to the 'compact' parameter by explaining it projects a slim summary with specific fields (bid, name, brewery, etc.), and clarifies that 'username' can be omitted for the own account. This adds value 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?

The description clearly states it 'Get[s] the distinct (unique) beers a user has ever checked in, with their rating and check-in count per beer.' This specific verb-resource combination distinguishes it from sibling tools like untappd_user_checkins (individual checkins) and untappd_beer_info (single beer details).

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 a clear directive: 'Omit username for your own account.' This tells the agent when to omit the parameter. It also mentions 'Supports sorting and paging,' which guides usage. However, it does not explicitly compare to alternatives or state when not to use this tool.

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