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

Annotations already flag destructiveHint=true and openWorldHint=true, so the mutation and external-email profile is declared. The description still adds real context beyond them: the attendee receives an email containing a self-serve rescheduling link, and the optional reason is forwarded verbatim to that attendee. It stops short of saying whether the cancellation can be undone or what happens if the attendee never rebooks.

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?

Three short sentences with the action front-loaded and no filler. The closing sentence about the reason being emailed slightly restates the earlier 'with an optional reason' clause, but it clarifies audience, so the repetition is close to earning its place.

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 two-parameter destructive mutation with no output schema, the definition covers the essential mechanics: what is cancelled, who is notified, and how the reason is used. The remaining gap is outcome handling — what the caller gets back and what state the booking is left in — which is modest given the small surface.

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?

bookingUid is fully documented in the schema, but rescheduleReason has no schema description at all (50% coverage). The description partially compensates by marking the reason optional and revealing that it is emailed to the attendee, which is meaning the schema does not carry, but it says nothing about length limits, formatting, or whether the reason appears in any other notification.

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 states a concrete verb and effect: cancel the booking and email the attendee a link to pick a new time, with an optional reason. That is far more specific than the title alone. It does not explicitly contrast itself with the sibling tools cancel_booking or reschedule_booking, which is the only thing keeping it from a 5.

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?

The line 'Ask the user — never choose for them' gives an explicit interaction rule, so the agent knows it must get consent rather than acting unilaterally. However, it never states when to pick this tool over reschedule_booking (host-driven rescheduling) or cancel_booking (cancel without reschedule), leaving the routing to inference from the sibling names.

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