Get Untappd friend activity feed

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

The description explicitly states 'Read-only', aligning with the readOnlyHint annotation. It also describes pagination behavior with max_id. No additional behavioral traits (e.g., rate limits) are mentioned, but the annotations already provide safety info, so the description adds value beyond the schema and annotations by confirming the pagination pattern.

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 extremely concise: two sentences totaling 24 words. It front-loads the main purpose and includes essential usage details without any filler. Every sentence serves a clear purpose.

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?

Given the tool's simplicity (3 params, no output schema), the description covers purpose, ordering, pagination, and safety. It lacks a brief note on the response structure (e.g., that it returns a paginated list of check-ins), but the annotations and context signals provide enough for an agent to infer behavior. It is nearly 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?

The input schema covers all three parameters with descriptions (100% coverage). The tool description adds context by associating max_id with pagination from a prior call, but this is a minor enhancement over the schema description. Therefore, the baseline of 3 is appropriate.

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 'your Untappd friend activity feed — the recent check-ins from people you follow, newest first'. This distinguishes it from sibling tools like untappd_beer_activity or untappd_local_checkins by specifying it's for the friend feed. The pagination detail adds further clarity.

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 implicitly tells when to use the tool: to view the friend activity feed. It also explains how to page backwards using max_id. However, it does not explicitly exclude alternatives or provide guidance on when not to use it, which would improve this dimension.

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