cancel_booking

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

With no annotations, the description carries the full burden and does well: it flags TWO-STEP, WRITES to the account, and that the default is a non-mutating preview. It doesn't state irreversibility, what happens if the cancellation window has passed, or auth/error behavior, but the safety profile is substantially disclosed.

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?

Front-loads the action in the first sentence, then the two-step/safety guidance, then the preconditions. Every sentence earns its place with no filler.

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 3-param mutation tool with no annotations and no output schema, the description covers the risky path and the preview mode well. The remaining gap is where the required club_uuid and class_id come from (presumably search_classes), which an agent would need to infer from siblings.

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 0%, so the description must compensate. It fully explains the critical 'confirm' parameter (default false previews, true cancels), but says nothing about class_id or club_uuid — not their format nor where to obtain them — leaving two of three parameters undocumented anywhere.

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 ('Cancel the user's booking for a class') and implicitly delimits itself against the sibling write tool book_class and the read-only search tools. An agent can tell immediately that this is the destructive counterpart to booking.

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 clear conditional guidance ('confirm=false (default) previews; confirm=true cancels') plus a hard prerequisite ('Only cancel after the user explicitly agrees') and a pre-check ('Check the cancellation window first'). It stops short of naming any alternative tool, though cancellation has no real sibling substitute.

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