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

readOnlyHint=true already signals a safe read, so the description's job is to add context beyond that. It does: it discloses the identity of the returned items (title, slug, covered releases/activities, visible attendee fields) and names the underlying Tito endpoint, which helps the agent reason about freshness and scope. It stops short of describing pagination behavior despite page/page_size parameters existing.

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?

A single front-loaded sentence states the resource and its return contents, followed by a terse endpoint reference. No padding or repetition, though the endpoint fragment is arguably optional decoration rather than decision-relevant 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 usefully enumerates what each check-in list contains, covering the return shape. Combined with the schema's descriptions of account resolution (TITO_ACCOUNT, tito_whoami) and pagination, an agent has enough to invoke this correctly; only pagination behavior is left unstated in prose.

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 baseline is 3. The description adds nothing about the parameters — it does not mention pagination, the event_slug requirement, or the optional account_slug/TITO_ACCOUNT fallback, all of which the schema already documents well.

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?

States a specific verb (List) and resource (an event's check-in lists) and clarifies the domain jargon with a parenthetical gloss ('the door lists used at the venue'). It also names the concrete fields returned, so an agent can distinguish it from sibling list tools like tito_list_tickets or tito_list_registrations without opening the schema.

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?

Usage is implied by the 'list' verb and the event-scoped resource, and the parenthetical hints at the real-world scenario (venue door lists). However, there is no explicit when-to-use guidance, no statement of prerequisites, and no pointer to alternative tools for related data such as tito_list_releases or tito_list_activities.

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