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

Annotations carry only destructiveHint=true, and the description adds two behaviors not in structured data: sparse/PATCH semantics ('only the fields you pass are sent') and the no-email side effect. It does not explain the destructive aspect the annotation flags (that the tags array replaces existing tags), which is the one notable gap.

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 tight sentences front-load the purpose and the two behavioral caveats, followed by the underlying PATCH route. The trailing 'Tito: PATCH /:account/:event/tickets/:ticket_slug' is marginally redundant but useful grounding and costs one line.

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 10-parameter, nested-object mutation with no output schema, the description covers the essentials: partial-update semantics, side effects, and the endpoint being wrapped. It stops short of describing what a successful call returns or warning that tag replacement is the destructive operation, but nothing critical to invoking it correctly is absent.

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 every parameter is already documented, including the tags-replacement caveat and the account_slug/TITO_ACCOUNT fallback. The description's field list is a restatement of parameter names, adding little beyond the schema; baseline 3 applies.

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 ('Correct a ticket's attendee details') and enumerates the mutable field families (name, email, company, phone, tags, metadata). It also proactively rules out a nearby behavior ('unlike a reassignment, which this server does not do'), so an agent can separate it from ticket-creation and other siblings 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?

It gives clear operating context: only supplied fields are sent (partial update), and no notification email is triggered. It doesn't name a competing sibling tool to prefer in a specific scenario, but the exclusions it does state remove the main ambiguity an agent would have.

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