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

Beyond the destructiveHint=true annotation, the description discloses the refusal condition (refund changed or no longer full amount), the downstream effect (cancels with the supplier, refunds traveller in full), and the irreversibility with real money. It also explains the retry semantics that back idempotentHint.

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 precondition, then the payload, then failure handling, then effects — good ordering. Loses a point for redundancy: "Cannot be undone" and "Real money, cannot be undone" restate the same warning across two adjacent 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 destructive, open-world mutation with a nested payload and no output schema, the description covers precondition, refusal behavior, retry path, and side effects. It does not say what a successful call returns, which is a minor gap given there is no output schema.

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 67% and both string params already carry descriptions, but the description adds real meaning the schema does not: cancellation_ref must come from anywayr_quote_cancellation and refund must be the exact amount it showed. The nested refund object itself is only constrained structurally, not semantically, in either place.

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 and resource ("Cancels a booking") plus the exact scope that qualifies it (the traveller asked to cancel). It explicitly names the sibling it depends on, anywayr_quote_cancellation, so the agent can distinguish this confirm step from the quote step without reading either 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?

Gives an explicit precondition (only when anywayr_quote_cancellation said confirm_in_chat), tells the agent what values to pass and their provenance, and names concrete alternatives on failure ("then quote again or use the review link"). Nothing is left to inference.

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