create_escrow

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

The description discloses key behavioral traits: funds are locked until completion or dispute resolution, and a risk-based premium is calculated. This goes beyond a simple mutation statement, although permissions and error handling are not mentioned. With no annotations, this provides good transparency.

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 (approx. 7 lines plus Args) and well-structured with a clear purpose paragraph followed by parameter details. No redundant information, though the Args section could be integrated more tightly.

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 no annotations, the description covers the tool's purpose, parameters, and core behavior. It lacks specification of the return value (e.g., escrow ID) and prerequisites, but is otherwise fairly complete for a creation 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?

Schema description coverage is 0%, so the description must compensate. It includes an Args section with each parameter's purpose and example values (e.g., buyer_agent_id: 'agent_weather_v2'). This adds significant meaning beyond the schema titles, though not exhaustive.

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 creates an escrow for agent transactions, with specific verb "Erstellt" and resource "Escrow fuer eine Agent-Transaktion". It explains the core function and is distinct from sibling tools like get_escrow_status or list_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?

No explicit guidance on when to use this tool vs alternatives. The description does not provide context for when this tool should be selected over other escrow-related tools like open_dispute or release_escrow.

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