cal_cancel_booking

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

No annotations provided, so the description must disclose behavioral traits. It states 'Cancel' (implying mutation) but omits side effects, permissions needed, reversibility, or error conditions (e.g., if booking is already canceled). For a cancellation tool, this is insufficient.

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 very short (two sentences) and front-loads the core purpose. It lists parameters efficiently. However, it could be slightly more structured (e.g., grouping param details). Still, no 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?

With no output schema, no annotations, and low schema coverage, the description is incomplete. It does not explain what the tool returns (e.g., confirmation, error codes), any constraints (e.g., time limits for cancellation), or the effect on the booking. The description alone is insufficient for an agent to use the tool safely.

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?

With 0% schema description coverage, the description must add meaning. It repeats parameter names and marks required/optional but offers no explanation: 'uid' is implied as booking UID but not confirmed; 'cancellationReason' is left as any string with no guidance (e.g., free text vs predefined values). This adds minimal value over the schema structure.

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') and resource ('booking') in the first sentence, and the 'by UID' clarifies the identifier. This distinguishes it from siblings like cal_create_booking, cal_get_booking, and cal_reschedule_booking.

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?

No guidance on when to cancel vs reschedule or other alternatives. While required and optional parameters are listed, there is no context about prerequisites (e.g., only future bookings) or situations where cancellation is appropriate.

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