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

The description adds the irreversibility warning ('cannot be undone') and the side effect that Appointedd may notify customers according to organisation settings. These details go beyond annotations, though it does not cover permissions, response behavior, or idempotency context that annotations imply.

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 description is front-loaded with 'WRITE (cannot be undone)' and then proceeds directly to scope, side effects, alternative, and endpoint. Every sentence earns its place and there is no 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 simple one-parameter destructive cancel, the description covers irreversibility, notification side effects, sibling differentiation, and the endpoint. Combined with annotations and schema, an agent has enough to invoke it correctly.

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?

There is one parameter and schema description coverage is 100%, so the schema already documents booking_id fully. The description adds no additional meaning about the parameter beyond the endpoint path template, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource: cancel a whole booking. It explicitly distinguishes this from appointedd_cancel_booking_customer, which handles removing one customer from a group booking. An agent can identify the correct sibling without opening either 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?

It names the alternative tool and the condition that selects it: use appointedd_cancel_booking_customer to remove one customer from a group booking. This makes the whole-booking scope explicit and prevents misuse.

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