Get nearby Untappd check-ins

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

Annotations already declare readOnlyHint=true, so the description's 'Read-only' adds minimal value. It does not disclose additional behaviors such as pagination, rate limits, or error conditions. The description adds some context about real-time data but not enough to fully inform.

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 states main function, second adds optional radius and read-only nature. No redundant or filler content.

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?

With no output schema, the description should hint at return format. It says 'what people are drinking nearby' but does not specify structure (e.g., list of check-ins with details). Appropriately assumes agent understands check-in concept, but could be more explicit.

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 coverage is 100%, so baseline is 3. The description mentions 'Optionally widen the search radius' for the radius parameter but provides no additional meaning for lat, lng, limit, or compact beyond what is in 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 tool retrieves recent check-ins near a location using lat/lng, specifying it shows what people are drinking nearby. It distinguishes itself from sibling tools like untappd_checkin (for posting) and untappd_user_checkins (for user-specific 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?

The description indicates the tool is read-only and optionally allows widening search radius, but does not explicitly list when to use versus alternatives. However, the purpose is clear enough for an agent to choose correctly among siblings.

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