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

Annotations only declare destructiveHint=true; the description goes further by disclosing sparse-update behavior (omitted fields are untouched) and a hard business rule (price is immutable once tickets are sold), plus the underlying endpoint. It does not cover permissions/auth requirements or failure modes, but it adds meaningful context beyond the annotation.

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?

One compact sentence plus a short endpoint suffix, front-loaded with the mutate-the-ticket-type action. The field list and the price caveat are relevant; the raw endpoint reference is marginal for an agent but cheap and harmless.

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 17-parameter mutation tool with no output schema, the description supplies the two things the schema cannot: that this is a partial update and that price changes are blocked post-sale, on top of a destructiveHint annotation. It stops short of covering auth needs, error conditions, or what a successful response contains.

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% across all 17 parameters, so the schema already carries formats, patterns and constraints. The description only groups the fields by theme (name, price, capacity, sales window, visibility), which is a mild navigational aid rather than new semantic detail — 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 ('Change a ticket type') and enumerates the mutable field groups (name, price, capacity, sales window, visibility), so the agent immediately knows this is an in-place modification rather than creation. It never names a sibling such as eventbrite_create_ticket_class, so differentiation is inferential rather than explicit.

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 description implies when to use it (modifying an existing ticket class, versus creating one) but gives no explicit alternatives or routing guidance to eventbrite_create_ticket_class or eventbrite_update_event. The 'only the fields you pass are sent' note is genuinely useful invocation guidance, but it is patch semantics rather than a when-to-use rule.

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