escrow__fund_escrow

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

The description explicitly mentions 'idempotent' and 'exactly-once' semantics, which are important behavioral traits beyond the basic action. However, it does not cover error cases (e.g., what if escrow is not OPEN) or side effects beyond funding. Given no annotations, the description adds good value but could be more thorough.

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 extremely concise: two sentences that front-load the core purpose and then add key detail about the parameter. Every sentence earns its place; no wasted words.

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 annotations or output schema, the description should explain more about return values, expected behavior (e.g., success/failure indicators), and prerequisites. It omits what happens if the escrow is not in OPEN state or if the payment_ref is malformed. The agent may be left with insufficient guidance for correct invocation.

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 explains that payment_ref 'links the payment-rail transaction', adding meaning beyond the schema. However, escrow_id is not elaborated. With 0% schema description coverage, the description partially compensates but leaves one parameter without additional context.

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 action: 'Mark an OPEN escrow as FUNDED' with idempotent semantics. It specifies the resource (escrow), the state transition (OPEN to FUNDED), and links to payment_ref. This distinguishes it clearly from sibling tools like open_escrow, release_escrow, etc.

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?

While the description implies this tool is used after opening an escrow and before release/refund, it does not explicitly state when to use it versus alternatives. No 'when not to use' or list of alternative tools is provided, leaving the agent to infer from context.

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