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

Annotations already declare readOnly=false, destructive=false, idempotent=false, so safety basics are covered. The description adds nothing beyond them: it doesn't say whether this is a partial or full replacement update, whether omitted fields are cleared, or what permissions are needed — meaningful gaps for a mutation tool.

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?

A single efficient sentence with no filler, and the resource scope is front-loaded. But it is short because it omits required information rather than because it is dense, so conciseness here is under-specification.

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 needn't be described, but with 8 parameters at 13% coverage an update tool should at least state partial-update semantics and which fields are mutable. The description leaves an agent unable to call this correctly without guessing.

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 only 13% — just event_id is documented. Six of the eight parameters (name, amount, quantity, is_enabled, description, ticket_type_ids) carry no schema descriptions at all, and the description does not compensate by explaining what any of them do or which are optional.

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) and resource (ticket addon) narrowed to one record within a given event. The 'update_*' naming plus the addon/event scoping makes it distinguishable from create_addon and delete_addon, though it never explicitly names those siblings.

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?

There is no guidance on when to use this versus create_addon/delete_addon, no prerequisites (e.g., that the addon must already exist, or that event_id must come from search_events), and no statement about which situations call for a partial update.

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