Get Untappd friend activity feed

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

The description explicitly states 'Read-only,' matching the readOnlyHint=true annotation, and adds useful behavioral context beyond annotations: the feed is limited to friends' check-ins, sorted newest first, and pages backwards with max_id. It does not mention authentication or rate limits, but the annotations already establish the safety profile.

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 three short sentences that front-load the core purpose, then add useful scope/order details, paging instructions, and a safety note. Every sentence earns its place with no redundancy or filler.

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?

For a read-only feed tool with no output schema, the description adequately conveys that the result is a newest-first list of friends' check-ins and references pagination metadata. The input schema fully documents parameters. It could be more explicit about the full response envelope, but the pagination.max_id reference and view parameter description cover the essentials.

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 baseline is 3. The description adds operational meaning beyond the schema by explicitly instructing the agent to page backwards using max_id from a prior call's pagination.max_id, which clarifies the parameter's role in a multi-call flow.

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 uses a specific verb phrase ('Get your Untappd friend activity feed') and defines the resource as 'recent check-ins from people you follow', with ordering 'newest first.' This clearly differentiates it from siblings like untappd_user_checkins or untappd_trending without requiring their schemas.

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?

It gives clear context: this is the authenticated user's friend activity feed, not a user, venue, or local feed. It also explains how to page through results by instructing to use max_id from a prior call's pagination.max_id. It stops short of explicitly naming alternatives or when not to use the tool, so I deduct one point.

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