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

Annotations already declare destructiveHint=true, but the description adds real information beyond that: the change affects the client's booking and cannot be undone through the API. It does not disclose secondary effects such as client notifications, refunds, or cancellation-fee behavior, which a destructive operation would ideally mention.

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 tight sentences, front-loaded with the action, followed by the critical irreversibility warning and the API mapping. Every sentence carries distinct information with no padding.

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?

With only two parameters, full schema coverage, no output schema, and destructiveHint already present, the description covers what an agent needs to call it safely. Missing only peripheral detail such as whether the client is notified or whether cancellation fees apply.

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 100% and both parameters (appointment_id required, reason optional) are documented in the schema. The description only restates that the reason is optional, adding no extra semantics such as supported formats or examples, so the baseline of 3 applies.

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 (Cancel) plus resource (an appointment), and the irreversibility note makes clear this is distinct from intakeq_update_appointment, which modifies rather than terminates a booking. An agent can select it without opening the schema.

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 contextual guidance: this is irreversible via the API and the recovery path is to book a new appointment. It does not explicitly contrast with intakeq_update_appointment or state when cancellation is appropriate, so it falls short of the full when/when-not bar.

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