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

Annotations already flag this as mutating (readOnlyHint=false, destructiveHint=true), and the description goes well beyond that: only supplied fields change, booking and customer records are untouched, the booking ticket PDF is regenerated on attendee changes, and metadata is merged per-entry rather than replaced. It also discloses that a null name clears while email cannot be cleared at all.

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?

Four sentences, all carrying operational weight, with the purpose front-loaded before the list_tickets prerequisite. Slightly dense, and the metadata merge rule is stated twice (once in prose, once in the schema), but there is no filler.

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?

An output schema exists, so return values need no explanation. For a 4-param mutation tool the description covers prerequisites, side effects (PDF regeneration, untouched booking/customer records), merge-vs-replace semantics, and the concurrent-writer caveat. Nothing an agent needs before invoking it is missing.

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 null-deletion semantics, key/value limits, and email normalization are already documented in the schema. The description largely restates those rules (null deletes a metadata key, null clears the name) rather than adding new semantics. Baseline 3 applies when the schema carries the parameter detail.

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 (update) plus the bounded resource (attendee name/email and metadata on one event ticket) and the scope of what it does not touch. An agent can separate it from update_ticket_type, update_customer, or update_event without opening a schema. The 'one event ticket' framing makes the unit of work unambiguous.

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?

Names the discovery path explicitly ('use `list_tickets` first to discover the ticket ID by attendee name, email, or ticket short ID'), which is the practical blocker for calling this tool. It also adds a caution ('confirm the target ticket before calling') and a real operational exclusion ('avoid replace-everything sync patterns' because door staff also write metadata).

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