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

With no annotations, the description must carry the burden, and it does disclose that funds are actually locked (a mutation with financial consequence) and that the tool charges a 0.5% fee — useful cost information rarely found elsewhere. It omits what release/verification requires, who can trigger release, and whether the escrow can be cancelled or refunded, which are important behavioral gaps for a funds-locking operation.

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?

Four short sentences, each carrying distinct information (purpose, locking behavior, return fields, price), front-loaded with the action. No filler, though the return-value sentence is slightly redundant boilerplate given it is not the primary concern.

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 no-annotation, no-output-schema mutation tool, the description usefully compensates by naming the returned fields (escrowId, status, amount locked) and the fee. It still leaves the lifecycle — how the escrow is later verified, released, or refunded, and which sibling handles that — entirely to the agent's guesswork.

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 all four parameters (amount, description, payerId, payeeId) are already documented in the schema. The description adds only the currency context ('amount locked') and the fee calculus, not new per-parameter meaning, so the baseline 3 applies.

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 ('Create an escrow') plus a scope qualifier ('for an agent-to-agent deal'), so the intent is unambiguous. It does not, however, distinguish itself from the many escrow siblings (pabandi_request_escrow, pabandi_start_escrow, pabandi_escrow_lock), which an agent could easily confuse with this one.

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 phrase 'for an agent-to-agent deal' hints at the context but gives no explicit when-to-use rule, no prerequisites (funded payer, registered identities), and no guidance on when to pick this over request_escrow or start_escrow. The agent must infer routing from sibling names alone.

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