list_ticket_classes_for_sale

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

With no annotations provided, the description must disclose behavioral traits. It implies read-only behavior but does not mention pagination (despite the continuation parameter) or any other operational details. The agent is left guessing about output format, limits, or side effects.

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?

The description is a single, focused sentence with zero redundancy. It is appropriately sized and front-loaded, delivering the core purpose immediately. Every word earns its place.

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 paginated list tool with a sibling (list_ticket_classes), the description is incomplete. It does not explain pagination behavior, what 'on-sale' means, or how this differs from the general list. Even with an output schema, the agent lacks critical context for correct 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 0%, so the description must explain parameters. It implicitly clarifies event_id via 'for an event', but the continuation parameter (pagination token) is completely undocumented. The agent has no idea what to pass or how to page through results.

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 states the exact verb ('List'), the resource ('ticket classes'), and a specific scope ('currently on-sale for an event'). It clearly distinguishes this from the sibling list_ticket_classes by the 'on-sale' qualifier, so an agent can tell them apart.

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?

No guidance is provided on when to use this tool versus list_ticket_classes or other alternatives. The description is purely declarative and does not mention conditions, prerequisites, or exclusions.

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