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

Beyond the annotations (idempotent, non-destructive), it discloses the retry/idempotency model (server derives upstream order id and Idempotency-Key from quoteId+orderId), that no funds move, that unpaid orders expire at no cost, that fees come only from the quote, and that the receiving Stellar address signs one transaction only when new or lacking a USDC trustline. This is unusually rich operational context.

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?

Purpose is front-loaded in the first sentence and almost every clause carries operational weight (idempotency, expiry, fees, amountPolicy, signing). It is nonetheless a dense wall of text where a short bulleted structure would aid scanning, so it is efficient but not optimally structured.

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 mutation tool with no output schema it covers the full lifecycle: returned handles (fundingId, deposit address, suggested amount, amountPolicy min/max, payBefore, accepted chains/tokens), idempotent retry, expiry, fee sourcing, and the exact-amount vs any_amount policy. Nothing an agent needs to call it correctly appears 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 meaning beyond the schema: orderId only needs to be unique among the caller's own orders because the server derives the upstream id and Idempotency-Key from quoteId+orderId, and planDigest must come from the same quote. That is genuine semantics the schema does not carry.

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 first sentence states a specific verb and resource plus scope: 'Turn an approved quote into a payable order,' and later clarifies 'Creates an order but moves no funds.' It names the upstream sibling (stellar_wallet_quote) by tying quoteId/planDigest to it, but never explicitly contrasts itself with the closely related create_deposit_order sibling, so differentiation is implied rather than stated.

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 establishes clear preconditions (an approved quote, planDigest from the same quote) and operating rules: pay once before payBefore, and retry with the same quoteId+orderId to get the same order. It stops short of explicit when-not-to-use guidance versus alternatives like create_deposit_order or the quote tool itself.

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