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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the description doesn't need to re-establish that this is a mutation. It does add genuinely new behavioral context: the two-phase confirmation handshake and the need to surface consequences to the user before committing. It does not spell out exactly what is lost or whether side effects (notifications, calendar events) occur.

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 sentences, zero filler, and the core action is front-loaded ahead of the confirmation mechanics. Every clause carries operational weight.

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 three-parameter tool with no output schema, the definition covers what the agent most needs: the action, the confirmation loop, and the retry discipline. Missing only the consequences detail (what the attendee loses, whether the booking host is notified) that would make it fully self-sufficient.

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 all three parameters (attendeeId, bookingUid, confirmToken) are already documented in the schema, including the first-call/second-call semantics for confirmToken. The description reinforces that the retry must use the SAME arguments, which is a useful emphasis but largely restates the schema. Baseline 3 is appropriate.

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 and resource: "Remove an attendee from a booking." The intent and target are unambiguous, and the sibling add_booking_attendee is obviously the inverse even though it is not named explicitly. It stops short of the 5-level because it does not name which alternative to reach for (e.g., cancel_booking vs remove_member).

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?

Gives concrete procedural guidance: first call returns CONFIRMATION_REQUIRED, tell the user what will happen, then retry with the same arguments plus confirmToken. That is actionable when-to-use instruction a caller would otherwise get wrong. It lacks explicit when-not-to-use guidance relative to siblings like cancel_booking.

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