Get Untappd user check-ins

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds the 'Read-only' statement and explains pagination direction and default ordering, which goes beyond the annotations by detailing operational behavior.

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 with no redundancy. The main purpose is front-loaded, and every phrase adds value (ordering, content, pagination, user hint).

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, the description adequately summarizes the return fields (beer, rating, comment, venue, toasts/comments). It mentions pagination metadata (max_id) implicitly. Could be more explicit about the response structure, but sufficient for a list retrieval tool with a standard resource.

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 description coverage is 100%, so the schema already documents each parameter. The description reinforces the purpose of max_id and the username omission rule but adds marginal new meaning beyond the schema.

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 verb 'Get' and the resource 'user's recent check-ins', specifying what is included (beer, rating, comment, venue, toasts/comments) and ordering (most recent first). It distinguishes from sibling tools like untappd_checkin_info or untappd_beer_activity by focusing on the user's timeline.

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 explicit pagination guidance ('Page backwards with max_id') and a conditional usage hint ('Omit username for your own'). Does not explicitly exclude alternative tools, but the context is clear enough for an agent to decide when to use this tool.

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