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

Annotations only give generic hints (readOnlyHint=false, idempotentHint=false, openWorldHint=true); the description adds the substantive facts an agent needs: the call is free, it creates a record but moves no funds, it returns quote_id, exact payment instructions (amount, asset, network, pay_to, expiry), a 1.45 XRP-equivalent fee, and an estimated destination amount. It also discloses the per-asset self-serve caps, which the annotations cannot express. No contradiction with readOnlyHint=false since a quote record is still created.

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 'FREE' and the route scope, then returns, then behavior, then next step – a sensible ordering with no filler sentences. It is somewhat long and repeats the amount caps that already live in the schema, which is the only waste.

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?

With no output schema, the description carries the return-value burden and does so: it enumerates the returned fields and the fee. Combined with the workflow handoff to n9t2_bridge_submit_payment and the OTC escalation path, an agent has everything needed to call this 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 description coverage is 100%, so the baseline is 3. The description does add the fee-on-top rule and the caps/OTC escalation for source_amount, but it largely restates what the schema's own field descriptions already say, adding little new parameter meaning.

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 ('Get a live, firm quote') plus the exact resource and scope ('move funds both ways between native XRP on the XRP Ledger and BTC on Bitcoin, BNB, USDT or USDC on BNB Chain (bsc), or USDC or ETH on Base (12 live routes)'). This cleanly separates it from siblings n9t2_bridge_submit_payment and n9t2_bridge_receipt, which are named or implied as distinct steps.

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?

Explicitly says creating a quote moves no funds, prescribes the workflow ('Next: customer approves and pays in their own wallet, then call n9t2_bridge_submit_payment'), and gives a when-not path: transfers above the self-serve caps go to the OTC desk at boss@n9t2.com. An agent knows both the next call and the escalation condition.

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