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

Goes well beyond the annotations: it stays marked cancelled (explaining destructiveHint=false), every registered customer is emailed the cancellation template with an optional note, the return value is the notified-customer count, per-call confirmation is on by default, and a Cotlet API key scoped to this app is required. Handles the 'reaches other people' consequence, though it never states whether the cancellation is reversible.

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 core content is duplicated almost verbatim ('Cancel one class. It stays on the customer schedule marked as cancelled.' appears twice), wasting roughly a third of the text. The preamble, cancellation effect, email behavior, confirmation policy, and auth note are also interleaved without a clear front-load.

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?

No output schema exists, yet the description covers the return value (customers notified), the side effects (email blast, schedule marking), the confirmation policy, and the auth requirement. Only the reversibility/undo question is left open for a mutation tool.

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 both parameters are already documented. The description adds that the note lands in the cancellation email, which is useful, but gives no syntax or ID-format guidance 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+resource ('Cancel one class') and clarifies what a class cancellation means (the session stays on the schedule marked cancelled). It does not explicitly distinguish itself from the close sibling momence_cancel_booking, which an agent must infer from the resource noun alone.

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?

Usage context is implied (cancelling a class session, class_id obtained from list_classes) but there is no explicit when-to-use or when-not, and no routing vs momence_cancel_booking. The confirmation/opt-out line is procedural rather than a selection guideline.

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