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

With no annotations, the description carries the behavioral burden. It discloses the authorization model (pilot can cancel only own bookings; admin can cancel any), which is the key safety-relevant behavior. It does not state whether cancellation is reversible or whether it affects settlement, but the core mutation is clear.

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 front-loaded with the core purpose and is compact, though the all-caps 'ULTRA-PROACTIVE' block is somewhat emphatic. Every sentence carries operational weight and no filler is present.

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 one-parameter mutation tool with no output schema, the description covers purpose, permissions, and ID sourcing. It could also mention edge cases such as already-canceled bookings or failure responses, but nothing essential to invoking the tool correctly is missing.

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 schema already documents bookingId at 100% coverage, so the baseline is 3. The description adds value by telling the agent exactly how to obtain the ID (from get_my_bookings or the previous create_booking success message), which goes beyond the schema's generic 'ID of the booking to cancel.'

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 opens with the specific action 'Cancel a booking,' naming both the verb and the resource. It then adds a clear scope distinction between pilot and admin permissions, which separates it from read-only siblings like get_my_bookings and from creation/settlement tools.

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 explicitly states when the tool applies and provides a concrete decision path: use get_my_bookings to find the ID or reuse the internal ID from create_booking, and never ask the user for an ID the agent can derive. This is direct when/when-not guidance.

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