Post Instances Quotes

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

Adds substantial behavior beyond the annotations: the quote expires 5 minutes after creation, is single-use, expires_at is epoch milliseconds, and it names the downstream endpoints that consume the quote. These lifecycle constraints are exactly what an agent needs and are not in the annotations.

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?

A single dense, front-loaded paragraph where each sentence carries information. Slightly run-on toward the end, but no filler and no repetition of the schema.

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?

No output schema exists, but the description flags the key response detail (expires_at in epoch ms) and the single-use lifecycle. It could say more about the quote response shape, but for a nested-body quote tool with rich schema descriptions it is largely complete.

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?

With only 33% schema coverage, the description compensates for the most important gaps: it explains request_amount in cents, currency_type as sender-vs-receiver, and the mutual exclusivity of bank_account_id/payable_id. It doesn't touch several object params (partner_fee_id, refund_wallet_address, network/token choices), so it doesn't fully close the coverage gap, but it covers the critical semantics.

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 ('Prices a payout') that clearly separates it from the sibling quote endpoints (PayinQuotes, TransferQuotes, QuotesFx). An agent can tell this is the payout-quote tool without opening the 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 clear operational conditions: send exactly one of bank_account_id or payable_id, and explicitly routes the agent to the correct execution endpoint afterward (EVM Create Payout for managed wallets, Solana/Stellar payout endpoints for self-custody). It lacks an explicit when-not-to-use statement versus the other quote tools, but the context is strong.

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