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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds the returned fields (id, name, dates, location, presale window, price overrides) and the underlying endpoints, but says nothing about pagination behavior beyond the schema or about what auth/visibility constraints govern non-public dates.

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 compact sentences: purpose and scope first, then payload contents, then endpoints. Nothing is wasted, though the trailing endpoint URL sentence is largely redundant given the tool name and adds little for an agent already choosing the tool.

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 11 optional parameters, no output schema, and rich annotation coverage, the description does enough — it names the returned attributes and both call modes. Pagination flow (page/next_page, page_size limits) lives entirely in the schema and is not echoed, which is acceptable but leaves the description slightly thin on multi-page behavior.

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 coverage is 100%, so all 11 parameters are already documented, including the event-omission rule and date filters. The description only echoes the dual scope implied by the optional event parameter and adds no syntax or interaction detail beyond the schema; 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 and resource ("List the dates (sub-events) of an event series") and clarifies the two scopes: one event or all series of an organizer. That phrasing separates it cleanly from pretix_list_events (series) and pretix_get_subevent (a single date), and the endpoint paths reinforce the distinction.

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?

Makes the selection condition explicit for the main branching decision: supply an event slug for one series, or omit it to span all series of the organizer. It stops short of naming alternatives such as pretix_get_subevent for adjacent detail or when to prefer pretix_list_events.

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