list_escrows

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

Discloses that expired escrows are automatically detected and mentions return fields (ID, status, parties, amount, risk score). No annotations exist, so description carries full burden; it is mostly transparent but could mention pagination or read-only nature.

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?

Seven sentences, front-loaded with main purpose. Some redundancy between first two sentences, but overall concise and structured. Every sentence adds value.

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 0% schema description coverage, the description covers parameter behavior and return fields adequately. Could mention if results are paginated or sorted, but sufficient for a listing tool.

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 fully compensates by explaining each parameter: status enum values, agent_id matching both buyer/seller, limit range (1-100) and default (20). Adds meaning well beyond bare schema.

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?

Clear verb 'list' and resource 'escrows'. Description states it lists all escrows with optional filters, distinguishing it from sibling tools that perform specific actions like create or release escrows.

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?

Implies usage for browsing all escrows with filters, but lacks explicit when-to-use vs alternatives. The sibling tool list makes it clear this is for listing, but no direct exclusions are stated.

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