Pay an order into escrow

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

With no annotations, the description carries the full burden and delivers: keys stay local, gas is paid in ETH, funds are escrowed rather than paid out until release, retries are idempotent against double payment, and encoding mismatches are refused. The main omission is what happens on failure or what the call returns, which matters for a money-moving tool with no output 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?

Front-loaded with the action, then rails, then preconditions, then the preview pointer. It is dense and long but every clause conveys a distinct behavioral fact; little could be cut without losing safety-relevant information.

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?

For a three-parameter mutation tool with no annotations and no output schema, the definition covers signing paths, gas, escrow custody, idempotency, balance and amount validation, and sequencing relative to the preview tool. Only the return payload is undescribed, which is a minor gap given the rest of the coverage.

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 0%, so the description must compensate, and it does: order_id drives the payment-instruction rebuild, and expected_amount_usdc and expected_chain_id are explained as optional assertions checked before signing. It stops short of stating the expected format of expected_amount_usdc beyond the schema pattern, but the semantic guardrail role of each parameter is clear.

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?

Names a specific verb and resource (pay an order) and immediately distinguishes the two rails it can take: x402 signing versus direct escrow with approve plus createEscrow. An agent knows exactly what operation is performed and can separate it from sibling tools such as agoreum_preview_payment or agoreum_settle_order.

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 tells the agent to call agoreum_preview_payment first, defines preconditions for use (order must still be awaiting payment, no escrow may already exist), and states refusal conditions for chain/amount mismatches and encoding differences. The when-to-use and when-it-will-refuse guidance is unusually complete.

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