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

Annotations provide only destructiveHint=true, so the description usefully adds PATCH partial-update semantics and the fact that no email is sent to anyone. The destructive behavior implied by the annotation (tags replace existing values) is only documented in the parameter schema, not the description, which is a minor 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 dense sentences, front-loaded with the purpose and fields, followed by the two most important behavioral caveats (partial update, no email). Nothing is wasted and the API endpoint is appended as compact reference.

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 mutation tool with no output schema, the description covers what it changes, how partial updates behave, and the notification side effect. It stops short of describing the response payload, error behavior, or permission requirements, which an agent might still want.

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 the schema already documents all ten parameters, including the important note that tags replace existing tags. The description's field list (name, email, company, phone, tags, metadata) mirrors the schema without adding formats, constraints, or edge-case behavior, so it earns only the 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?

The description states a specific verb ('Correct') and resource ('a ticket's attendee details') and enumerates the affected fields (name, email, company, phone, tags, metadata), so an agent knows exactly what the tool mutates. It distinguishes itself from reassignment semantics, though it does not explicitly differentiate itself from sibling tools like tito_get_ticket or tito_create_ticket.

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 makes the usage context clear: this is for correcting attendee details, it is a partial update ('Only the fields you pass are sent'), and it does not trigger notifications. The 'unlike a reassignment, which this server does not do' clause scopes what this tool is not for, but no sibling tool is named as an alternative.

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