untappd_search_brewery

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

No annotations provided, and the description offers no behavioral details (e.g., pagination, rate limits, authentication requirements, or any side effects). The agent has no insight into how the search works or what to expect.

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, short sentence, which is concise but critically underspecified. It lacks essential details, so it does not achieve effective conciseness.

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 search tool with no output schema and no annotations, the description is incomplete. It fails to inform the agent about the format of results, potential pagination, or any constraints. The absence of parameter descriptions further reduces completeness.

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?

The input schema has 2 parameters (query, api_key) with 0% description coverage. The description does not explain the purpose of 'query' (e.g., brewery name, location) or 'api_key' (e.g., optional key for authentication). Without additional context, the agent cannot infer correct usage.

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 (search) and resource (breweries) on Untappd. It is straightforward but lacks explicit scoping (e.g., by name or location) and does not differentiate from sibling tools like untappd_get_brewery or untappd_search_beer.

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 such as untappd_get_brewery for specific brewery details or untappd_search_beer for beer. No context on prerequisites or query formatting.

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