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

Beyond the annotations (which already flag destructive, idempotent, openWorld), the description adds substantive context: funds_moved false, a signed receipt being returned, the 0.10 USDC x402 charge and free-call quota, X-Wever-Wallet-Proof binding arguments to the path, and the 300 USDC escrow cap. These are real behavioral facts an agent could not infer from the schema. It does not say what happens to downstream state after the withdrawal or whether it can be undone.

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 purpose is front-loaded and correct, but the body degenerates into a run of short declarative clauses, several of which are operator boilerplate ('API access fees are separate from travel spending', 'Booking approval is separate from quote selection'). Some earn their place (funds_moved false, idempotency, reconciliation path); others dilute the operational details.

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, paid, three-parameter mutation with no output schema, this is nearly complete: it states the returned artifact (signed withdrawal receipt), the payment model, the proof mechanism, the escrow cap, test-mode behavior, and a reconciliation route. The remaining gap is the parameter-level meaning, which the schema does not supply and the description does not fill.

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 description coverage is 0% across three required parameters, so the description carries the full burden and largely fails. It never explains what trip_id identifies, that leg_id picks which saved leg (flights/hotel/tickets/table) is withdrawn, or how idempotency_key should be chosen for retries. 'Per-leg principal approval' and the wallet-proof binding hint at per-leg scoping and canonical arguments, but only obliquely.

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 opening sentence gives a specific verb and resource: 'Withdraw one saved quote selection from your trip and return a signed withdrawal receipt.' That is enough to separate it from wever_sports-book-leg (which creates a selection) and wever_sports-trip-status, though it never names those siblings to make the distinction explicit.

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 clear routing context: 'Uncertain attempts are reconciled through trip-status' tells the agent when to stop retrying and switch tools, and 'Booking approval is separate from quote selection' scopes the action. It stops short of an explicit when-not-to-use statement or a direct pointer to book-leg as the counterpart operation.

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