Get recent check-ins for a beer

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

Annotations already indicate readOnlyHint=true; description adds 'Read-only' and specifies that check-ins are public. Also details what data is returned (rating, comment, venue), partially compensating for missing output schema. 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 sentences: first defines purpose and output, second gives paging guidance. No superfluous text, front-loaded with essential information.

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?

Despite no output schema, description covers key return fields (who, rating, comment, venue) and explains paging behavior. Could be more exhaustive (e.g., timestamps) but sufficient for typical use.

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; description adds context for max_id (paging from prior call) and explicitly links bid to beer ID. Adds value beyond schema definitions.

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 verb 'Get' and resource 'recent public check-ins for a beer', identifies bid, and lists returned data (who drank, rating, comment, venue). Clearly distinguishes from siblings like untappd_beer_info or untappd_user_checkins.

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?

Provides paging guidance using max_id but lacks explicit when-to-use or when-not-to-use advice relative to sibling tools. Does not mention alternatives or exclusions.

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