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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the underlying endpoint and that availability fields are conditionally included, but says nothing about pagination behavior or result volume beyond what the schema already states ('Can be slow on big events').

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 covering purpose and payload, plus the endpoint for reference. Minor waste in the duplicated word ('with with_availability') and the endpoint restates structured context, but overall tight.

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 usefully enumerates what the response contains (size, covered products, closed state, availability counts), which is exactly what an agent needs to decide whether to call it. Only the subevent filtering nuance is left to the schema, which handles it well.

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%, so every parameter (page, page_size, organizer, event, subevent, with_availability) is already documented. The description only echoes the with_availability effect, adding no syntax or semantics beyond the schema — baseline 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?

States a specific verb and resource ('List the quotas (capacity pools) of an event') and enumerates the payload fields (size, covered products, closed state, availability). This makes it distinguishable from the single-quota sibling pretix_get_quota_availability, though it never names that sibling 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?

Usage is implied by the field list and the parenthetical 'with with_availability, how many are still available' hints at when to enable that flag, but there is no explicit when-to-use/when-not guidance and no pointer to pretix_get_quota_availability as the alternative for a single quota's availability.

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