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

Annotations supply only destructiveHint=true and a title, so the description usefully adds the scope semantics and the underlying POST endpoint. It does not disclose authorization requirements, whether a duplicate code is rejected, or any limits on code creation, leaving meaningful behavioral gaps for a mutation tool with thin annotations.

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 tightly packed sentences, front-loaded with the type taxonomy and followed by the scoping rules; the Eventbrite endpoint is a compact trailing detail. Nothing is redundant given 11 parameters.

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 and only a destructiveHint annotation, the description carries the burden for a complex 11-parameter mutation. It covers creation types and scoping adequately, but omits what is returned, permission prerequisites, and failure behavior, so it is complete only at the level of construction, not consequences.

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 the baseline is 3, but the description contributes real added meaning by tying individual parameters into mutually exclusive scopes (event vs group vs organization), which the flat schema does not express as a rule. It stops short of clarifying the amount_off/percent_off exclusivity beyond what the schema already says.

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 (Create) plus the three concrete artifacts it can produce, and names the enum value that selects each: coded promo code, public discount, access code unlocking hidden tickets. It also states the scoping model, so an agent can distinguish this from list_discounts/update_discount without opening schemas.

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?

Gives explicit conditional guidance on which parameters select which scope: event_id (+ticket_class_ids) for one event, ticket_group_id for a group, neither for an org-wide discount. It does not name alternatives such as eventbrite_update_discount or eventbrite_list_discounts, nor state when not to create, so it falls short of a full 5.

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