Evaluate Escrow Work

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

Annotations already indicate readOnlyHint=false and destructiveHint=true, setting the expectation of a state-changing operation. The description adds valuable behavioral context: payment releases automatically on approval, hashes are auto-verified, and it details the exact return structures for PASS and FAIL. No contradictions with annotations.

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 well-structured with a clear opening, a key behavioral note, and a concise breakdown of return values. It is slightly repetitive (hash verification appears both in the description and schema) but overall efficient and front-loaded with the core purpose.

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?

The description is complete for an agent to invoke it correctly: it explains the purpose, the automatic payment behavior, the verification process, and both possible return formats. The output schema is present, so return values are fully specified. All parameters are documented in the schema, and the description covers the essential behavioral nuances.

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 coverage is 100% and each parameter has a clear description. The description repeats the hash verification for the work field, which the schema already provides. It adds no additional parameter-specific meaning beyond the schema, so a baseline of 3 is appropriate.

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 opens with a clear verb+resource ('Submit proof of completed work against an existing escrow vault'), specifies the automatic payment release, and distinguishes it from sibling tools like create_escrow_vault and confirm_escrow_transaction by focusing on the evaluation action. It is unambiguous and precise.

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 provides clear context for when to use this tool (to prove work against an escrow vault, useful for NFT transfers, token payments, etc.) and states that approval auto-finishes without EscrowFinish. It does not explicitly exclude alternatives, but the intended use case is well-defined and distinct from siblings that create or confirm escrows.

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