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

The description goes well beyond the annotations by detailing concrete consequences: permanent deletion, no canceled status, removal of the Zoom meeting and calendar event, and emailing the customer. It also states that execution is immediate and cannot be undone. This fully discloses the behavioral impact of a destructive operation.

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?

Every sentence earns its place: the first states the core action, the second lists side effects, and the third conveys immediacy and irreversibility. The description is front-loaded with the most important information and is not padded with redundant phrases.

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 single-parameter destructive tool with a rich output schema, the description covers the essential contextual needs: where the ID comes from, what will be destroyed, what side effects occur, and that the operation is irreversible. The output schema being present means return-value details are not required here.

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 coverage is 100%, and the only parameter, appointmentId, is already documented as 'From get_bookings'. The description repeats this origin but does not add new format, validation, or semantic detail beyond what the schema supplies, so the baseline 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 action, 'Cancels a booking', and explicitly differentiates it by saying it PERMANENTLY DELETES the booking rather than changing its status. It also names the exact resource type (a booking identified by appointmentId) and distinguishes itself from siblings like reschedule_booking and create_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?

The description clearly indicates the booking source ('appointmentId from get_bookings') and the permanent, irreversible nature of the action, which implies use only when a booking must be fully removed rather than rescheduled. It does not explicitly name reschedule_booking as an alternative, so it stops short of a 5.

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