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

Annotations already declare destructive=true, readOnly=false and non-idempotent, but the description adds genuinely new behavioral detail: this is a soft delete via a status flag plus an enqueued cleanup job, which tells the agent the effect is asynchronous. It stops short of stating reversibility or what the cleanup job actually purges.

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 sentence that front-loads the action and scope, then the mechanism. No filler and no repetition of the title or schema.

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?

Annotations cover the safety profile and an output schema covers returns, so the description only needs to carry the operational nuance it already does. However, for a destructive mutation on an attendee it omits downstream consequences (tickets, orders, group memberships) and how this differs from ban_attendee, leaving a real gap for correct tool selection.

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 100% with both parameters explicitly documented (user_id, event_id), so the schema carries the semantics. The description only restates that the event scopes the operation; it adds nothing about format or validation 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 (delete) and resource (one attendee) scoped to a provided event, and even discloses the mechanism (mark deleted + enqueue cleanup). It does not distinguish itself from sibling operations like ban_attendee or remove_attendees_from_groups, which share the 'make this attendee go away' surface.

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?

No when-to-use or when-not-to-use guidance is given. With siblings such as ban_attendee, remove_attendees_from_groups, and update_attendee, an agent must guess whether deletion, banning, or group removal is the intended operation; the description offers no routing criteria or prerequisites (e.g., pending orders, ticket refunds).

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