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 REST path and the field inventory, which tells the agent what a call returns, but says nothing about error behavior for missing events or permission requirements.

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 field list followed by the endpoint path — no filler. The raw GET path is marginally redundant with the tool's function but is compact and useful for agents mapping to the REST API.

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 compensates by listing the returned fields, which is the main gap it needed to fill for a simple read tool. Annotations handle the safety profile, and the only unaddressed area is failure/permission behavior, a minor omission for a read-only getter.

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 the note that organizer is optional for a single-organizer token, so the schema carries the parameter burden. The description adds no parameter-level syntax or hints beyond that, making 3 the appropriate baseline.

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+resource ('One event in full') and enumerates exactly which fields come back, so it is clearly a single-resource fetch rather than a listing. It doesn't explicitly name pretix_list_events as the contrasting sibling, though the singular framing strongly implies it.

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 singular 'one event' implies you use this when you already have an event slug rather than to browse, and the schema's cross-reference to pretix_list_events supports that. However, the description itself states no when-to-use, no prerequisite, and no alternative for the list case.

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