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

With annotations covering destructiveness and idempotency, the description adds meaningful operational context: the cancellation frees capacity, sends transactional notifications, and requires a one-time approval from a protected form. It does not contradict the annotations and enriches the behavioral picture beyond the structured hints.

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, each earning its place. The critical precondition is front-loaded, followed by behavior and retry semantics, with no filler.

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?

The description covers authorization, idempotency, and side effects for a destructive mutation, and an output schema exists so return values need not be explained. However, three of five required parameters remain undocumented, and no alternative sibling tool is named, leaving gaps for correct invocation.

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 only 20%, so the description must compensate. It adds some meaning for the authorization token and idempotency key, but source, anonymous_session_id, and correlation_id receive no explanation in either the schema or the description.

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: it cancels the authorized active booking, frees capacity, and sends notifications. It does not explicitly distinguish this tool from related siblings such as reschedule_service_booking or prepare_service_booking_change, so sibling differentiation is left to the name and title.

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 gives a clear precondition: use only with the one-time approval issued after the user confirms the exact cancellation inside the protected management form. It also specifies that safe retries must reuse the same idempotency key. It does not name alternative tools or explain when to use those instead.

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