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

Annotations only supply readOnlyHint=true; the description adds substantive behavioral context by enumerating the per-attendee fields returned (checked_in, cancelled, refunded, status, ticket_class_name, profile, barcodes) and noting barcode status values. It does not cover pagination semantics or rate limits, but it adds genuine value beyond the annotation.

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 tightly packed sentences: scope and granularity first, then the returned fields, then the invocation constraint and REST endpoints. No filler; every clause carries information an agent needs.

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 helpfully enumerates the return fields and both endpoints, and the schema covers pagination and filtering params. Minor gaps remain around ordering and page-size behavior, but nothing essential for a correct call is missing.

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 already 100%, so the baseline is 3, but the description adds a crucial constraint absent from the schema: event_id and organization_id are mutually exclusive and one is required (the schema declares no required params and enforces no oneOf).

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 attendees') plus the granularity ('one per sold ticket') and the two supported scopes (single event OR all organization events). An agent can distinguish it from the singular sibling eventbrite_get_attendee without opening a schema.

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?

Gives an explicit invocation constraint ('Pass exactly one of event_id / organization_id') and clarifies the two access patterns, which is real usage guidance. It stops short of naming an alternative tool or stating when-not to use it (e.g. versus get_attendee or list_orders).

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