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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds the non-obvious fact that the result contains personal data, which matters for how an agent handles and surfaces output. It does not discuss pagination or result caps, though the schema documents limit/offset defaults.

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?

Two compact sentences: purpose and returned fields first, then available filters, then data-sensitivity and read-only flags. No filler and nothing important buried.

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, listing name/email/ticket type/time slot/state/checkout answers in the description is exactly the compensation needed. Only pagination behavior and result-size expectations are left implicit, and those are handled by the schema.

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 coverage is 100%, so limit, offset, match, states, eventId and timeSlotIds are already documented in the schema. The description restates the filter dimensions (state, text match, time slot) without adding syntax or matching behavior 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?

States a specific verb and resource ('List the attendees (ticket holders) of an event'), and clarifies what an attendee is versus an order, which separates it from universe_list_orders. It also enumerates the returned fields, so the agent knows exactly what data comes back.

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 implies usage by saying filter by ticket state, text match or time slot, but it never states when to call this instead of universe_list_orders or universe_list_ticket_types. The 'ticket holders' framing hints at the boundary without making it explicit.

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