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

Annotations already mark the operation read-only and non-destructive. The description goes beyond that by disclosing the 200-item limit, the fields returned (ticket status and type), and the truncated flag that signals when results exceed the cap. It does not describe pagination or what to do when truncated, but the disclosed behavior is meaningful and consistent.

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 communicates the action, resource, limit, output fields, and truncation behavior with zero filler. Every element 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?

With no output schema, the description adequately summarizes the response as ticket status, ticket type, and a truncated flag. Combined with the well-described inputs and read-only annotations, an agent can invoke it correctly. Minor gap: it does not explain what to do if truncated or whether additional attendee fields are present, but this does not block correct usage.

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%, and the parameter descriptions are strong: eventId is tied to list_events, org is scoped to list_my_orgs and only needed in multi-org contexts. The tool description itself adds no parameter details, but the schema carries the full burden, so the baseline score of 3 is appropriate.

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 action verb 'List', identifies the resource as 'ticketed attendees for an event', and adds concrete scope: up to 200, ticket status and type, and a truncated flag. This clearly separates it from sibling tools like list_events and get_registration_stats, leaving no ambiguity about the tool's function.

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 clear context: use this tool when you need ticketed attendee details for a specific event, with an explicit 200-record cap. It does not explicitly name alternatives or exclusions, but the read-only, event-scoped purpose is unambiguous enough for an agent to select it correctly.

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