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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds useful context annotations cannot: the exact fields returned and the underlying endpoint GET /attendees/{attendeeid}, which is valuable given there is no output schema.

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 tight fragments with the resource and returned fields front-loaded and no filler. The trailing endpoint path is slightly redundant with the tool name but still delivers routing value.

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 single-parameter read tool with no output schema, the description compensates well by listing the returned fields and the endpoint. Only the lack of explicit guidance on failure or unknown-id behavior keeps it from being fully complete.

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 single attendee_id parameter is documented in the schema, including where to obtain it (the id field in eventzilla_list_event_attendees). The description says 'by id' but adds no format, range, or edge-case meaning beyond the schema, so baseline 3 applies.

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 (get), resource (attendee), the identifying key (id), and enumerates exactly what is returned: name, ticket type, barcode, check-in status, order reference, registration answers. This clearly separates it from the sibling eventzilla_list_event_attendees, which returns many attendees.

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 singular 'one attendee by id' implies the single-record use case versus the list sibling, and the id is implicitly sourced from the list tool, but the description never explicitly states when to use this instead of eventzilla_list_event_attendees or what to do if the attendee is unknown.

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