eudr_create_milestone_escrow

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses the milestone stages and optional split structure but says nothing about irreversibility, required wallet approvals, funding dependencies, permissions, or the relationship to release/fund escrow tools, all critical for a financial escrow creation operation.

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 sentence with the verb and resource front-loaded, and the parenthetical stage breakdown is dense but relevant. It is efficient, though the stage percentages partially duplicate the milestone_weights default already in the schema.

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?

For a complex 11-parameter financial escrow mutation with no annotations and no output schema, the description is incomplete. It does not explain prerequisites, post-creation lifecycle, funding steps, or how the agent should proceed after creation, leaving significant gaps for correct invocation.

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 100%, so the schema already documents all 11 parameters, establishing a baseline of 3. The description adds a mapping between stages and the default milestone weights (30/40/30), but does not add substantial semantics beyond what the schema provides for split_recipients, chain, or wallet fields.

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?

States a specific verb ('Creates') and a specific resource ('3-Stage Milestone Conditional Escrow agreement'), and adds detail about optional first-mile split payouts and stage weights. However, it does not distinguish this tool from siblings such as eudr_create_agent_escrow or eudr_create_payment_order, so an agent must infer the difference from the name alone.

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 explains what the tool creates but gives no explicit guidance on when to choose it over alternatives, no prerequisites, and no exclusions. With many escrow-related siblings, this omission leaves routing to inference.

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