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

Adds substantial context beyond the destructiveHint/readOnlyHint annotations: irreversibility and the required user confirmation, the side effect of cancelling every booking and returning membership/credit, default attendee notification, the $1 apology credit via emergency-cancel flow, and the required 'book' scope. This is exactly the behavioral detail annotations do not carry.

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 sentences, front-loaded with the core action, followed by side effects and the irreversibility caution. The scope requirement tag is compact and useful; no filler or repetition.

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 destructive tool with no output schema, the description thoroughly covers what happens to bookings, credits, notifications, and the confirmation workflow. The only gap is that it does not state what a successful call returns, so an agent must infer how to confirm completion.

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 75%, so the schema already documents notify, apology_credit, and confirm_class_name. The description adds marginal context (the 'standard $1' credit and emergency-cancel flow) but does not document class_session_id, which lacks a schema description, so it stays at the baseline.

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 an entire class session in MarianaTek'. The word 'entire' plus 'every booking is cancelled' distinguishes it from per-client tools like remove_client_from_class and from cancel_membership, even though no sibling is named explicitly.

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 description implies when to use it (when the whole session must be cancelled) and provides workflow guidance, but it never names alternatives or states when-not conditions. The agent must infer the boundary against siblings such as cancel_membership and remove_client_from_class on its own.

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