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

Annotations already declare readOnly=true, destructive=false, so the safety profile is covered; the description adds value beyond that by disclosing that responses contain attendee personal data and that ticket secrets are stripped. It does not describe pagination behavior or result-size expectations, which keep it short of a 5.

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, front-loaded with what the payload contains, followed by the privacy note and the endpoint. Minor awkwardness in the 'check in by position id' fragment, but nothing wasted.

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 12-parameter read-only list tool with no output schema, the description usefully enumerates the key returned fields and flags PII and secret-stripping. Pagination and the interplay of ignore_status with order__status are left to the schema, which is a reasonable division but not 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%, including enum meanings and page/next_page guidance, so the baseline is 3. The description contributes only the indirect note that positions carry ids usable for check-in, not any filter semantics beyond the schema.

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 opens by naming the resource and its scope ('The attendee list of a check-in list') and enumerates the returned fields (attendee name, product, order code, check-in history, attention flag), so an agent can tell what this returns. It also hints at the boundary with the check-in tool ('check in by position id'), though the sibling is not named 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?

The line 'check in by position id' implies this list is a precursor to pretix_checkin_position, which is useful routing. However, there is no explicit guidance on when to prefer this over pretix_list_order_positions, pretix_get_checkin_list_status, or when ignore_status / order__status should be used, leaving selection mostly to inference.

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