eudr_create_agent_escrow

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the escrow is immutable, that funds are locked until EUDR compliance is proven, and that it targets default risk, which is real signal. However, it omits critical operational behavior: what happens at expiry (the schema's expiry_hours default of 72 suggests auto-refund, but the description never confirms it), who can trigger release, and what the caller must have already done (e.g., verified counterparty).

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?

Two tightly packed sentences with the core operation front-loaded and the value proposition trailing. The closing phrase 'Eliminates commercial default risk' is mild marketing padding but does convey the tool's purpose, so the waste is minimal.

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 10 parameters, 7 required, no annotations, and no output schema, the description is adequate but thin. It explains the concept well but leaves the agent without the lifecycle context needed to call it correctly in sequence (funding, release, arbitration, expiry behavior).

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 every parameter is already documented in the schema, establishing a baseline of 3. The description adds no syntax, format, or constraint detail beyond the schema, so it does not earn more.

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 gives a specific verb (Creates) and a precise resource (an immutable B2B trade Smart Escrow agreement), plus the mechanism (locking USDC in multi-chain vaults until EUDR compliance is proven). It implicitly distinguishes itself from escrow siblings like eudr_create_milestone_escrow and eudr_fund_agent_escrow by emphasizing the compliance-conditional, immutable nature, but it never names those siblings explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no pointer to the follow-up tools an agent would obviously need (eudr_fund_agent_escrow, eudr_release_agent_escrow, eudr_arbitrate_agent_escrow). Usage must be inferred entirely from the tool name and the compliance framing.

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