Get Untappd beer detail

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

Adds value beyond annotations by listing returned fields and explaining compact behavior. Annotations already state readOnlyHint, idempotentHint, openWorldHint, and description aligns with these. No contradictions.

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 efficient sentences: first packs all details, second references sibling tool. No extraneous words.

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?

No output schema, but description fully covers what is returned (list of fields) and effect of compact. Complete for a simple retrieval tool with informative annotations.

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%, baseline 3. Description adds context: 'Get a bid from untappd_search_beer' for bid, and 'unless compact' explains compact parameter effect, surpassing schema alone.

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?

Describes a specific action (Get full detail) on a specific resource (beer by bid), lists contained fields, and distinguishes from sibling tools like untappd_search_beer and untappd_brewery_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?

Explicitly tells how to obtain the bid from untappd_search_beer, and notes the tool is read-only, implying safe usage. Does not explicitly list exclusions, but the context of the tool's simplicity and sibling differentiation suffices.

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