escrow__open_escrow

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

No annotations provided, so description carries full burden. Discloses trustless, exactly-once semantics, fee frozen at open, and retry-safety. Lacks mention of permission requirements or side effects beyond state change.

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?

Concise, front-loaded, and well-structured. Contains all essential information without filler. Could be slightly more organized but effective.

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 8 parameters, no output schema, and no annotations, the description is incomplete. Explains retry-safety and fee computation but omits many parameter details and error conditions.

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%; only amount_minor and open_ref are explained in text. Other 6 parameters (payee, payer, terms, fee_bps, currency, deadline) lack any description. Inadequate compensation.

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 opens an escrow between payer and payee, differentiating it from sibling escrow tools like fund, release, refund, dispute. It specifies the verb 'open' and resource 'escrow', and adds retry-safety details.

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?

Provides clear context on when to use: for opening escrows. Mentions retry-safety with open_ref and duplicate behavior. However, does not explicitly state when not to use or compare to alternatives like direct settlement.

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