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

Goes well beyond the annotations by disclosing real-world effects: credit return, customer notification, late-cancellation charges governed by the Cancellation Policy setting, a default confirm-each-call behavior that can be toggled, and the API key requirement. These are the kind of consequences an agent needs before mutating a booking.

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?

Purpose and scope are front-loaded in the first two sentences, followed by the choice, policy, confirmation, and auth details. Slightly repetitive ('with credit and notification choices' restated later), but overall tight and each sentence carries distinct information.

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 mutation tool with annotations but no output schema, the description covers the needed ground: what changes (booking removed, credit/notification decisions), policy-driven charges, confirmation workflow, and the required API key scope. Only the return/result shape is unaddressed, which is acceptable without an output schema.

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%, so all four parameters are already documented, making 3 the baseline. The description's sentence about choosing credit/notification/late-cancellation maps loosely to the three booleans but adds no syntax or default-value detail beyond the schema.

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 one customer's class booking, and clarifies it is the per-customer action 'the same as Cancel booking next to the customer in the class'. This scoping distinguishes it in spirit from a whole-class cancellation, though it never names the sibling (momence_cancel_class) directly.

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 describes the decision points (credit, notify, late cancellation) and confirmation behavior, which implies usage context, but gives no explicit when-to-use vs alternatives guidance such as choosing this over momence_cancel_class or momence_remove_reservation-style siblings. Usage is implied rather than prescribed.

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