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

With no annotations provided, the description carries the transparency burden and does well: it discloses that funds are locked on-chain, the release/dispute flow, and that an arbiter reviews disputes. It does not mention gas costs, reversibility, or required authentication, but the core lifecycle behavior is well described.

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 two sentences, front-loaded with the core purpose, and the second sentence adds relevant behavioral detail about dispute resolution. The marketing phrase 'the only escrow service with real dispute resolution on Base' is arguably fluff but also communicates a unique value proposition; overall, every word earns its place.

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 no output schema, the description could explain what the tool returns (e.g., escrow ID), but it doesn't. However, the tool's purpose and lifecycle are thoroughly described, and sibling tools cover status/dispute/release, so the description is largely sufficient for an agent to use it 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?

The schema already provides full parameter descriptions with examples, bounds, and defaults (100% coverage). The description adds no additional parameter-level meaning—for instance, it doesn't explain how timelock_minutes interacts with the dispute flow beyond 'auto-refunds'. Thus the description does not exceed the schema baseline.

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 description clearly states the tool creates a USDC escrow with dispute resolution, using the specific verb 'Create' plus a specific resource. It distinguishes itself from sibling tools (escrow_dispute, escrow_release) by highlighting the built-in dispute resolution lifecycle, making the purpose unmistakable.

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 provides clear context for when to use the tool—when you want to lock funds in escrow with dispute resolution—and implies the flow (funds locked until release or dispute). However, it does not explicitly state exclusions or name alternatives like 'use safe_pay for simple payments', so it misses the full 'when-not-to-use' guidance.

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