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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond the annotations: it does not say whether deletion is permanent, what happens to attendees or orders referencing the addon, or whether the event must be in a particular state.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity reflects under-specification rather than disciplined economy.

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 destructive mutation tool this is thin: no cascade/irreversibility notes, no auth or event-state prerequisites, and one of two parameters is undocumented. The presence of an output schema excuses it from describing return values, but the rest of the burden is unmet.

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 coverage is only 50% — event_id is documented ("Event UUID returned by search_events") but addon_id has no description anywhere. The description does not compensate by explaining what an addon_id is or where to obtain it (e.g., from create_addon or read_event_content).

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 uses a specific verb and resource ("Delete one ticket addon") and scopes it to a single addon within an event, which is clear. It doesn't explicitly distinguish itself from update_addon or delete_ticket_type, but the verb+resource combination makes its domain 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?

There is no guidance on when to use this versus update_addon (to clear fields) or delete_ticket_type, and no prerequisites stated. An agent must infer entirely from the name that this is the removal path for an addon.

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