escrow__refund_escrow

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

Discloses behavioral traits such as the cancel equivalence for OPEN escrows and the 'exactly-once' guarantee. With no annotations, this provides key context beyond the obvious refund action.

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?

Two concise sentences that efficiently convey core purpose and a key nuance. No wasted words, appropriate length.

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?

Adequately covers use cases and behavior for a straightforward refund operation. Lacks explanation of return value or idempotency details, but no output schema exists to rely on.

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 description does not explain the 'reason' parameter at all, and 'escrow_id' is only implied. With 0% schema coverage, the description should compensate but fails to add meaning beyond the schema property titles.

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?

Clearly states the verb 'Refund' and the resource 'escrow' along with specific states (OPEN/FUNDED/DISPUTED). Distinguishes from siblings like 'release_escrow' by specifying 'to the payer' and noting that refunding an OPEN escrow is a cancel.

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?

Specifies eligible escrow states and notes the cancel behavior for OPEN escrows. However, it does not explicitly compare to alternatives like 'release_escrow' or 'dispute_escrow' or provide 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.