untappd_get_beer

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

With no annotations provided, the description carries full burden. It only says 'Get details', which implies a read-only operation, but does not disclose any behavioral traits such as authentication requirements (api_key parameter), rate limits, or whether the call is idempotent. For a fetch operation, more transparency is needed.

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 a single sentence of 7 words, perfectly concise and front-loaded. Every word is necessary and adds clarity. No unnecessary 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?

For a tool with no output schema and no annotations, the description is too brief. It does not elaborate on what 'details' are returned (e.g., name, ABV, rating, brewery info), leaving the agent to guess the response structure. Given the low complexity but high dependency on specific input, it is incomplete.

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 50% (only 'bid' has a description in the schema). The tool description adds no additional meaning for parameters. It does not mention that 'bid' is a numeric beer ID or that 'api_key' is required for authentication. The agent must infer from the schema alone, which is insufficient.

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 'Get details for a specific beer on Untappd', which specifies the action (get) and the resource (beer details). It distinguishes from sibling tools like untappd_search_beer (search) and untappd_beer_activities (activities) by focusing on a specific beer's 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 no guidance on when to use this tool versus alternatives (e.g., untappd_search_beer to find a beer first, or untappd_beer_activities for activity feed). It lacks context on prerequisites, such as needing a beer ID from a prior search.

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