escrow__fund_escrow

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

The description explicitly states the tool is idempotent, a key behavioral trait. With no annotations provided, this is valuable. However, it does not disclose other behaviors like failure modes, permission requirements, or what happens if the escrow is not in OPEN state.

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: one sentence plus a clarifying phrase. It front-loads the core purpose and includes idempotency and the role of payment_ref without any superfluous text.

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 tool with no output schema, the description does not explain return values or expected outcomes. It covers prerequisites implicitly ('OPEN escrow') and idempotency, but lacks details on response format or error scenarios.

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 schema has 0% description coverage for parameters. The description adds meaning for payment_ref ('links the payment-rail transaction'), but provides no additional context for escrow_id beyond its name. It partially compensates for the lack of schema descriptions.

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 the verb 'fund', specifying the resource and state transition. It distinguishes from sibling tools like open_escrow, release_escrow, refund_escrow, and dispute_escrow by naming the specific funding step.

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 description implies use after an escrow is open, as it says 'Mark an OPEN escrow'. However, it does not explicitly state when not to use this tool (e.g., if already funded) or provide alternatives. Usage context is clear but not fully detailed.

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