get_attendee_details

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

With no annotations, the description carries the full burden of behavioral disclosure. It does state that this is a read operation and enumerates returned content (profile, barcode, custom question answers), which is useful. However, it does not disclose behavior for missing attendees, permission requirements, or whether any returned fields can be null or omitted.

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?

The description is a single sentence with no filler or repetition. It front-loads the action and lists the key data categories, so every word 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?

This is a simple two-parameter get operation and an output schema exists, so the description does not need to explain return values. However, the lack of usage guidance and parameter semantics means an agent may not know when to choose this over list_event_attendees or how to interpret the attendee_id parameter.

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 0%, and the description does not mention event_id or attendee_id at all. The parameter names are somewhat self-explanatory, but the description adds no meaning about the relationship between the IDs, such as whether attendee_id is event-scoped or global.

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?

"Retrieve" is a clear action verb and the resource is specific: a full attendee profile, barcode, and custom question answers. This distinguishes it from sibling list tools like list_event_attendees and checkin_attendee, so an agent can tell what it does without opening the 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?

The description provides no guidance on when to use this tool versus alternatives such as list_event_attendees, get_order, or checkin_attendee. It only implies a single-attendee lookup through the verb "Retrieve," but never states the conditions or exclusions.

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