untappd_get_brewery

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

No annotations provided, so the description carries the full burden. It only says 'Get details', implying a read operation, but does not disclose any behavioral traits such as authentication needs (api_key is optional?), rate limits, or the structure of returned data. Lacks detail.

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, concise sentence that is front-loaded. However, it is overly brief and could benefit from more detail without becoming verbose. Still, it is not cluttered.

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?

Given the lack of output schema, annotations, and detailed parameter info, the description is incomplete for a data retrieval tool. It does not hint at what 'details' are returned, leaving the agent without sufficient context to judge the tool's utility.

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 0%, and the description provides no information about parameters. It does not explain what 'brewery_id' or 'api_key' represent or how to use them. The description adds no value beyond the schema field names.

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 the action (get details), resource (brewery), and platform (Untappd). It effectively distinguishes from sibling tools like 'untappd_search_brewery' which is for searching, and 'untappd_get_beer' for 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?

No guidance on when to use this tool versus alternatives. It does not mention that a specific brewery ID is required or that this tool is not for searching by name. No exclusions or context provided.

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