Get recent check-ins for a beer

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

Annotations already declare readOnlyHint and openWorldHint. Description reinforces 'Read-only' and adds pagination behavior (page backwards). No contradictions. The description adds context beyond annotations without repeating them.

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 states core purpose, second explains pagination. No unnecessary words, front-loaded, perfectly sized.

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 exists, but description lists returned fields (rating, comment, venue) and pagination detail. For a 4-parameter list tool, this sufficiently informs the agent of return structure and behavior.

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 covers 100% of parameters with descriptions. Description adds specific usage for max_id, clarifying it expects the pagination.max_id from a prior call. This improves understanding over 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?

The description clearly states the tool gets recent public check-ins for a beer by bid, including specific data fields (who drank, rating, comment, venue). This distinguishes it from siblings like untappd_beer_info (beer details) and untappd_checkin_info (single check-in).

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 describes pagination using max_id from prior calls. Does not specify when to avoid this tool versus alternatives, but the purpose is distinct enough. Could add exclusion criteria, but the guidance is clear.

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