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 by structured data. The description's marginal contribution is the list of returned fields plus the REST endpoint, but it says nothing about pagination behavior, token scoping for the optional organizer, or result ordering.

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 sentences, front-loaded with the purpose and returned fields, with the endpoint trailing as supporting detail. Slightly dense field enumeration but no filler.

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 eight parameters, no output schema, and a read-only listing role, the description covers the essentials and usefully enumerates the returned fields in place of an output schema. It could go further on pagination and on the organizer-token fallback, but nothing critical for calling it is missing.

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 all eight parameters are already documented in the schema; baseline is 3. The description only mentions the event scope and does not add semantics for the filter parameters (active, admission, search, category) or page/page_size.

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 products ... of an event') and parenthetically clarifies the domain terms (ticket types, merchandise). It is distinguishable from pretix_get_item by the plural 'List' verb, though it never explicitly contrasts with that sibling.

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 only implied by the verb — an agent can infer this is the bulk-fetch counterpart to pretix_get_item, but the description gives no explicit when-to-use or when-not-to-use guidance, and no mention of the available filters as a selection rationale.

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