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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description usefully discloses the returned fields (capacity, allocation_count, sold_out, date/times, attached releases) and the underlying endpoint, but says nothing about pagination behavior or scope limits.

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 dense sentence with the resource and returned fields front-loaded, plus the endpoint reference. Efficient with no filler, though the em-dash list is packed and could be trimmed slightly.

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 compensates by enumerating the key return fields, and pagination is handled by the schema. Requirements like the optional account_slug fallback are covered in the schema, so the definition is nearly complete for a simple list tool, lacking only deeper return-shape detail.

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 event_slug, account_slug, page and page_size are all documented in the schema itself. The description adds no parameter-level meaning beyond that, which matches the baseline 3 when structured data does the work.

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 activities), and clarifies scope with concrete examples (sessions, workshops, dinners beyond the ticket itself). This distinguishes it from sibling list tools like tito_list_tickets and tito_list_releases, though it doesn't name a sibling explicitly.

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 clause 'beyond the ticket itself' implicitly signals when to reach for this over tito_list_tickets, but there is no explicit when-to-use statement, no prerequisites, and no named alternative. Usage is inferable but not spelled out.

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