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

Annotations only carry destructiveHint=true, so the description must add most of the behavioral context — and it does: it discloses that the call creates a real reservation, consumes inventory, and may notify the customer, plus what the response contains (booking ids, invoice/payment URL). It stops short of idempotency, retry safety, or auth/permission requirements, which would be useful for a commit-style mutation.

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?

Front-loaded with the action, then inputs, side effects, follow-up tool, and return shape, closing with the raw API route. It is a single dense block with semicolon-separated clauses; every element earns its place, though the reference-heavy style makes it slightly harder to scan than short discrete sentences.

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 3-parameter mutation with a nested form object and no output schema, the description covers prerequisites (form fields via checkfront_get_booking_form), side effects (inventory consumption, customer notification), return values, and the modification path. Nothing needed to invoke it correctly appears to be 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real value beyond the schema: it explains that session_id and slip are alternative entry paths, gives example/tipically-required form keys (customer_name, customer_email), and points to another tool for the authoritative required-field list.

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?

States a specific verb+resource ('Commit a booking') and immediately distinguishes itself from siblings by naming checkfront_add_to_booking_session (session building), checkfront_get_booking_form (field requirements), and checkfront_update_booking_status (later changes). An agent can place this tool in the booking lifecycle without opening any other schema.

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?

Explicitly gives the two mutually exclusive input paths (from a session_id built via checkfront_add_to_booking_session, or directly from SLIPs) and routes the agent to checkfront_get_booking_form for required fields. It also names the follow-up tool for modifying the reservation, so when-to-use and when-to-use-something-else are both covered.

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