list_ticket_classes

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

There are no annotations, so the description carries the burden of behavioral disclosure. It does not mention that results may be paginated via the continuation parameter, nor does it clarify the meaning of 'all' when a continuation exists. The read-only nature is implied but not explicitly stated.

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 with no filler. The core purpose, object, and examples are all included without waste.

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 adequate for a simple list operation because the required event_id is inferable and an output schema exists. However, it leaves meaningful gaps: pagination through continuation is unmentioned, and the relationship to list_ticket_classes_for_sale is not clarified.

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 0%, so the description must compensate for the schema. 'for an event' loosely maps to event_id, but the continuation parameter is completely unexplained, leaving a required-to-optional parameter pairing partially undocumented.

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 uses a specific verb and resource: 'List all ticket classes... for an event.' The parenthetical '(admissions, VIP, booth packages)' adds concrete scope. The word 'all' also distinguishes it from the sibling tool list_ticket_classes_for_sale.

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 gives no guidance about when to use this tool versus list_ticket_classes_for_sale, get_ticket_class, or other ticket-class tools. It only says 'for an event,' which implies a context but does not explain the appropriate selection criteria or exclusions.

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