Prepare Escrow Transaction

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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description adds useful context beyond them: the output is a pre-filled transaction dict with ledger sequence, fee, and condition, and it clarifies that the buyer signs and submits outside this tool. It omits permission/auth requirements, so not a 5.

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-loads the core purpose, then gives the call sequence in short, purposeful sentences. Slightly long but nearly every sentence carries procedural information an agent needs.

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?

Output schema exists so return-value detail isn't required, yet the description still explains the return dict and the end-to-end sign/submit workflow, making it callable with minimal ambiguity. Missing only auth/permission notes.

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 parameters like escrow_id, amount_xrp, and the addresses are already documented. The description only alludes to the condition and pre-filled fields without mapping them to specific inputs, so baseline 3 is appropriate.

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 concrete verb and resource: 'Build a ready-to-sign XRPL EscrowCreate transaction.' It places itself in a workflow relative to create_escrow_vault and confirm_escrow_transaction, which distinguishes it from siblings. It doesn't explicitly name a sibling it replaces, so it stops short of a 5.

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?

Explicit prerequisite ('Call create_escrow_vault() first'), explicit follow-up ('Then call confirm_escrow_transaction() with the tx hash'), and a stated position ('the low-friction path'). The when-to-use sequence is fully spelled out, leaving nothing to inference.

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