escrow__list_escrows

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

The description only states the basic function. No annotations are provided, and the description does not disclose any behavioral traits such as read-only nature, data limits, pagination, or performance characteristics. This is a significant gap for an agent to understand side effects or constraints.

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 concise, consisting of one sentence plus a list of states. The prefix '[escrow — trustless escrow & settlement (exactly-once)]' is somewhat redundant with the tool name and module but does not detract significantly. Overall, it is efficient.

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 tool has a single optional parameter and no output schema. The description covers the filtering capability but omits details about return format, pagination, ordering, or error conditions. For a simple list tool, this is adequate but not thorough, given the lack of annotations.

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 lists the allowed state values (OPEN|FUNDED|RELEASED|REFUNDED|DISPUTED), adding meaning beyond the schema, which lacks a description for the state parameter. With 0% schema coverage, this is essential. However, it does not explain the meaning of each state or default behavior.

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 lists escrows and optionally filters by state, listing the possible state values. It distinguishes from sibling tools (e.g., open_escrow, release_escrow) by being a read-only listing operation, though it does not explicitly differentiate.

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 for listing escrows with optional filtering, but it provides no explicit guidance on when to use this tool versus alternatives like escrow_status or dispute_escrow. The context from sibling names helps, but the description itself lacks such guidance.

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