calmesh_cancel_booking

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

With no annotations provided, the description adds valuable behavioral context: it returns the booking ID and cancelled status, and it requires 'book' scope. This goes beyond the basic action to inform about output and authorization, though it does not cover edge cases like cancellation of already-cancelled bookings.

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 short sentences that are front-loaded with the core purpose. Every word contributes necessary information (action, target, ID, return, scope), with no repetition or fluff.

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 single-parameter cancellation tool, the description covers the essential aspects: what it does, how (by ID), what it returns, and a required scope. It lacks details on error conditions or idempotency, but these are not critical for such a straightforward operation.

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?

The input schema already fully covers the one parameter (booking_id) with its description. The tool description adds no additional parameter information, so it does not exceed the baseline of 3.

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 specific action ('Cancel'), the resource ('existing booking'), and the method ('by ID'). This unambiguously distinguishes it from sibling tools like calmesh_create_booking and calmesh_list_bookings.

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 offers clear context: use this tool when you have a booking ID and need to cancel it. It does not explicitly mention alternatives or exclusions, but the situation is clearly implied by the phrasing.

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