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

Annotations only declare readOnlyHint=true, and the description meaningfully extends that by enumerating what each attendee record carries (checked_in, cancelled, refunded, status, ticket_class_name, profile, barcodes with used/unused status) and by mapping the call to the underlying GET endpoints. It does not mention pagination limits or rate-limit behavior.

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?

Three tight sentences: scope first, then the disambiguating mutual-exclusion rule, then the API mapping. Every clause carries information and nothing is repeated from the schema.

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 read-only list tool with no output schema, the description supplies the return-record shape, the scope rule, and the endpoint mapping, and the schema covers pagination via continuation. The only gap is that page-size/termination behavior for pagination is left implicit.

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 the baseline is 3, but the description adds a cross-parameter constraint the schema cannot express: event_id and organization_id are mutually exclusive and exactly one is required (the schema marks neither as required). That is genuine semantic value beyond the structured fields.

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 precise verb and resource ("List attendees") plus the granularity ("one per sold ticket") and the two supported scopes (single event or all of an organization's events). This is clearly distinguishable from sibling get_attendee, though the description never names that 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?

It gives one concrete invocation rule ("Pass exactly one of event_id / organization_id"), which prevents a common misuse, but offers no guidance on when to prefer this over get_attendee, get_attendee_report, or list_orders. Usage is implied by the scoping sentence rather than spelled out.

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