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

Annotations already mark destructiveHint=true and readOnlyHint=false; the description adds more context: cancellation is irreversible, a reschedule is only committed after the new confirmation email, and failures leave the original time intact. It also gives the timezone format, which is crucial behavioral information.

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?

The description is efficiently written and front-loads the outcome. Each sentence adds value, including the timezone instruction and failure semantics. It's slightly long, but every clause serves a clear purpose.

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?

It covers all necessary items an agent needs to call this tool safely: the required user inputs, the newSlotId source, confirmation before cancellation, and time inconsistency. With a moderate 4‑parameter tool and no output schema, the description is sufficiently complete.

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?

The input schema has 100% description coverage and already documents bookingId, email, action, and newSlotId. The description adds a little extra (like the need to ask the user for email and booking reference), but doesn't fundamentally change parameter understanding beyond the schema, so the 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 clear, specific action: 'Cancels an existing yesmcp consultation booking (`action: cancel`) or moves it to a different window keeping the same reference (`action: reschedule`)'. It identifies the exact resource and distinguishes the two modes, making it easy to tell apart from siblings like book_consult or list_availability.

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?

It explains the prerequisites: ask for the booking reference and email before calling, and state that rescheduling uses a newSlotId from list_availability. It also tells the agent to confirm before cancelling. It stops short of explicitly saying to use a book_consult for a fresh window, but the contextual clues are strong.

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