escrow__release_escrow

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

The description discloses exactly-once idempotency semantics and that repeated calls return the existing record. However, without annotations, it lacks details on side effects, error conditions, or state transitions beyond the initial state constraint.

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 a single, dense sentence that communicates core behavior efficiently. The prefix '[escrow — trustless escrow & settlement (exactly-once)]' adds context but could be trimmed or integrated.

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 output schema and incomplete parameter documentation, the description does not fully equip an agent to use the tool. Missing return value format, error cases, and detailed parameter semantics reduce completeness.

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?

With 0% schema description coverage, the description adds no meaning to parameters. It does not explain 'escrow_id' format or 'delivery_proof' purpose, leaving the agent to infer from name and type alone.

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 'Release' and the resource 'escrow' with specific state conditions (FUNDED/DISPUTED). It distinguishes this tool from potential alternatives by being the sole escrow release tool among siblings.

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 usage when escrow is funded or disputed but provides no guidance on when not to use, prerequisites, or alternative tools. There is no mention of required authorization or state validation.

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