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

With no annotations, the description carries the full burden for a financial mutation. It says funds are 'released' but does not disclose irreversibility, permission or authorization requirements, what happens if deliverableHash does not match the locked hash, or whether release can be undone. Only the return values are mentioned.

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?

Three short sentences, front-loaded with the action and outcome, with no filler. The 'Requires escrowId' sentence is mildly redundant against the schema but is a defensible emphasis of the single mandatory argument.

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?

It covers the action and a partial return description (status and amount released) with no output schema to lean on, but for a fund-moving operation it omits preconditions, failure modes, and irreversibility. Adequate to call, not adequate to call safely.

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 coverage is 100%, so all three parameters are already documented, and the description's 'Requires escrowId' merely restates the required field. It adds no meaning for idempotencyKey or deliverableHash beyond what the schema says, 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?

The description gives a specific verb and resource: 'Release locked escrow funds to the recipient,' which an agent can distinguish from siblings like pabandi_escrow_lock or pabandi_escrow_waterfall. It does not explicitly name the contrasting siblings, so it falls short of a 5.

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 'locked escrow funds' hints that a prior lock step is a precondition, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many escrow siblings. The agent must infer the workflow context entirely.

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