Get nearby Untappd check-ins

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

The description correctly notes 'Read-only,' aligning with the readOnlyHint annotation, but adds no new behavioral insights beyond what annotations already provide.

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 highly efficient sentences convey purpose, optional parameter, and read-only nature with no redundant information.

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?

The description is sufficient given the presence of annotations and clear naming, though a brief note on return format (list of check-ins) would enhance completeness.

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?

With 100% schema coverage, the description adds minimal value by restating lat/lng and radius parameters; underlying schema already describes each parameter adequately.

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 coordinates, effectively distinguishing it from sibling tools like venue activity or 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 implies usage for nearby check-ins and mentions the radius option, but does not provide explicit guidance on when to avoid this tool or compare with alternatives like trending or search.

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