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

No annotations are provided, so the description carries the full burden and largely meets it: atomicity ('both legs succeed or both revert — no settlement gap'), the required vault state, the seller-side prerequisite, and a 4-step buyer workflow that makes clear the tool only produces JSON to be signed. It omits auth/permission or rate-limit details, 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-loaded with the one-line definition, then organized into modes, prerequisites, and a numbered workflow that maps to the actual call sequence. The prose is a little dense in places, but sections are scannable and every block carries actionable content.

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 an output schema present, the description needn't explain return values, and it instead supplies the surrounding context an agent needs: protocol semantics, mode selection, gating state, seller prerequisite, and post-call signing/submission steps. Nothing essential to correct invocation is 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 description coverage is 100% and the single parameter is already documented as the escrow vault ID. The description reinforces the PASS_AWAITING_NFT constraint, but adds no syntax, format, or lookup detail beyond what the schema states. Baseline 3 applies when the schema does the heavy lifting.

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 ('Returns a pre-built Batch transaction') and immediately names the exact protocol primitive (XLS-56 Atomic NFT DvP, TF_ALL_OR_NOTHING). The two modes are called out explicitly, so an agent understands this is the atomic-settlement payload builder rather than a generic escrow read. Distinguishable from siblings like submit_escrow_transaction or prepare_escrow, which do not return a one-signature Batch tx.

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 when to use each mode: AI audit + atomic settlement 'when the deliverable needs independent verification', and pure on-chain DvP 'for tickets, physical assets, collectibles'. It also states the prerequisite state (PASS_AWAITING_NFT) and the required seller registration step. It does not name a sibling tool as the alternative, so it falls short of full when-not routing.

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