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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorld=true, so safety is covered. The description adds genuinely useful context that the response nests variations, add-ons, and bundles, but says nothing about auth scope, 404 behavior, or whether add-ons/bundles are expanded vs. referenced.

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 short sentences, front-loaded with the payload description. The literal REST path is mostly redundant with the schema but is compact and does no harm.

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 simple read-only getter with full schema coverage and no output schema, the description discloses the one thing the schema cannot: that the returned product is aggregated with variations, add-ons, and bundles. Remaining gaps (error cases) are minor.

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 when the token sees one organizer. The path template in the description merely restates the three parameters already documented in the schema, adding no new semantics.

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: fetches a single product including its variations, add-ons, and bundles. This distinguishes it functionally from pretix_list_items, 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?

Usage is only implied: 'One product' versus the plural list tool signals that this is the single-record fetch. There is no explicit statement of when to prefer this over pretix_list_items or what happens if the item id is unknown.

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