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

The description provides rich behavioral context, including charging the chosen card, no pending state, and the exact spoken outcome to read. However, it says calling again with the same quote_id returns the same outcome and never books twice, which contradicts the annotation idempotentHint=false.

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 action and then proceeds through safeguards, expected answer handling, and retry behavior. Despite its length, every sentence supports a high-stakes booking flow and none is redundant.

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?

There is no output schema, but the description explains the only two outcomes, how to read the spoken line, that there is no pending state, and what happens on price changes or repeated calls. An agent has enough information to invoke and interpret the tool correctly.

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 schema already defines all three parameters. The description adds important operational meaning beyond the schema, especially that amount_cents_heard is a guard: if it differs from the quote, nothing is booked.

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 precise verb and resource: it books the hotel from a quote_route_hotel answer and charges the chosen card. It clearly distinguishes this confirmation step from the quoting step and names the sibling tool that produces the quote.

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 gives explicit when-to-use conditions: only after the person clearly said yes to the price read from the quote, never on a maybe, and never for a price they did not hear. It also covers the price-changed case and says to wait for a new yes before calling again.

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