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

With no annotations provided, the description carries the full burden and does exceptionally well. It discloses that the service checks the address before building escrow, reports if the transfer has not arrived, pays gas in relay mode, holds no key and signs nothing, derives the escrow address from the exact terms, and reports the seller's actual received amount separately from the creator fee. These are real behavioral details beyond the schema.

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?

The description is front-loaded with the core purpose and uses bold labels and warning blocks to make long content scannable. However, the sentence about seller and nominal_buyer accepting wallet or email addresses appears twice almost verbatim, which is unnecessary repetition. Otherwise, the length is justified by the two-mode complexity.

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?

Given the tool's complexity, missing annotations, and low schema coverage, the description is remarkably complete. It covers the prerequisite relationship with prepare_escrow_payment, both execution paths, a critical external_id constraint, the impact of altered terms, and receipt/fee semantics. An agent has enough context to call this tool correctly without additional investigation.

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 only 22%, so the description must compensate. It explains the meaning and interaction of the most semantically tricky parameters: seller/nominal_buyer email-to-wallet resolution, authorization/signature relay behavior, external_id provenance, and the relationship between amount, token_amount, and creator_fee. It does not individually define expiry_timestamp, token_symbol, or description, but those are more self-evident or have defaults.

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: 'Create the escrow around the money and return a signed receipt.' It also clearly distinguishes itself from the related prepare_escrow_payment by repeatedly referring to 'as prepared' and requiring the external_id returned by that tool, so an agent can tell this is the settlement/execution step rather than preparation or verification.

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?

The description explicitly says 'which one runs is decided by whether you pass a signature,' then gives two clear modes with exact conditions: omit authorization/signature if the transfer was already made, or pass them to have the service relay the payment. It also warns that external_id must be the one returned by prepare_escrow_payment. This gives an agent direct selection criteria.

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