Get recent check-ins at a venue

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

The readOnlyHint and openWorldHint annotations already cover safety and scope; the description adds meaningful behavior beyond them: it states the results are public, includes ratings/check-in content, and specifies that paging is backwards via a prior call's pagination.max_id. It does not detail auth or rate limits, but the annotation coverage lowers the bar and the added context is useful.

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?

Three short, high-signal sentences: the main action with result contents, the paging mechanism, and the read-only flag. There is no filler or repetition of schema fields.

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 venue check-in listing, the description conveys the core result contents and paging behavior, and the schema fully documents all parameters including view/limit behavior. With no output schema, a bit more response-envelope detail could help, but the description is sufficient for correct selection and basic invocation.

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 an extra practical detail for max_id—pointing to pagination.max_id from a prior call—and orients the agent around what the returned check-in records contain. This is a small but genuine increment 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 opens with a specific verb and resource: "Get the recent public check-ins at a venue by its id," and names the outcome data (who was there, what they drank, ratings). This clearly distinguishes it from venue search/info siblings and from user/beer/brewery activity tools.

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 establishes clear context: call by venue_id, returns public check-ins, and explicitly explains how to page backwards using max_id from the prior pagination.max_id. It does not name alternative tools or say when not to use it, so it misses the top score.

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