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

Annotations declare destructiveHint=true, and the description usefully scopes that destruction: it destroys the session and its held inventory, but explicitly states 'no booking is affected.' That scoping is genuine added value beyond the annotation. It does not mention auth requirements or whether the operation is reversible, keeping it from a 5.

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?

Three short clauses plus an endpoint line, all front-loaded with the core action and its effect. No filler; every sentence carries information an agent needs.

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 two-parameter mutation tool with no output schema and full annotation coverage, the description supplies the key consequences (inventory release, no booking impact) and the underlying endpoints. Sufficient to call correctly, with only minor gaps around reversibility/failure behavior.

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 enum already documents that 'end' closes and 'clear' empties, so the description largely restates the schema. It does not clarify session_id format or the default behavior beyond the schema, making the 3 baseline 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?

Opens with a specific verb+resource ('Abandon a booking session') and immediately differentiates the two modes ('clear' empties items, 'end' closes it). This cleanly separates it from siblings like get_booking_session and add_to_booking_session, which operate on the same session object without abandoning it.

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?

Signals its context clearly ('Abandon a booking session') and explains the consequence that drives the choice ('Releases the inventory it was holding; no booking is affected'). It does not explicitly name alternative siblings or state when-not-to-use, so it stops short of a 5 despite the clear semantic framing of clear vs end.

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