cancel_vip_booking_request

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

No annotations are provided, so the description carries full burden. It mentions ownership verification and valid statuses, but does not disclose other behavioral traits such as whether cancellation is irreversible, if it triggers notifications, or what happens on failure. Some transparency is present but incomplete.

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 two sentences, no redundancy. It front-loads the primary action and prerequisites, then adds a crucial status constraint. Every sentence adds value.

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?

Given the tool's complexity (4 params, no annotations, output schema exists), the description covers core usage and constraints. It lacks details on error handling or post-cancellation effects, but is sufficient for an agent to use it correctly in most cases.

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 0%, so the description must add meaning. It clarifies that booking_request_id, customer_email, and customer_phone are for verification, but cancellation_reason is only mentioned as an optional field without additional context. The description partially compensates for the schema gap but not fully.

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 clearly states the action ('Cancel a VIP booking request') and specifies the resource. It also distinguishes from sibling tools like create_vip_booking_request by naming the reverse operation and listing prerequisites.

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 provides clear context for when to use the tool: requires booking ID plus customer email and phone for ownership verification, and works only for submitted, in_review, or confirmed statuses. It does not explicitly mention alternatives or exclusions, but the status restriction gives strong usage guidance.

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