Get recent check-ins at a venue

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description reinforces this with 'Read-only' and adds pagination behavior ('page backwards with max_id'), providing useful behavioral context beyond annotations.

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 two sentences: one for core purpose and returned data, one for pagination and safety. It is front-loaded with the verb 'Get' and contains no filler, making it highly efficient.

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 lacking an output schema, the description explains what the response contains (who, what they drank, ratings). Pagination behavior is covered. Given the tool's moderate complexity (4 parameters, no nested objects) and the presence of annotations, the description is sufficiently complete.

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?

Parameter schema coverage is 100%, so the schema already documents all parameters. The description adds value by explaining the pagination intent of max_id and implicitly describing limit's default (though schema already states default 25). This enhances understanding beyond the 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 it retrieves recent public check-ins at a venue by ID, specifying the returned data (who, what they drank, ratings). This distinguishes it from sibling tools like untappd_venue_info or untappd_checkin_info that return different resources.

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 explicit pagination guidance ('page backwards with max_id') and declares the tool read-only. However, it does not explicitly state when to use this tool over similar ones like untappd_local_checkins or untappd_activity_feed, though the context is clear.

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