eudr_release_agent_escrow

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

No annotations provided, so the description must carry the full load. It discloses the release conditions, which is important pre-call context, but omits auth requirements, whether the action is irreversible, failure modes, or side effects. Partial transparency for a high-stakes financial 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?

Single sentence, front-loaded with the action and conditions. No waste.

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 the 4 parameters, high schema coverage, and no output schema, the description covers the core trigger but doesn't address post-release behavior, failure handling, or the role of the optional 'plots' parameter. Adequate but with gaps for a financial release 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 coverage is 100%, so the baseline is 3. The description mentions the trigger sources (customs code pattern, DDS reference) which map to parameters, but adds no format, validation, or interaction details beyond what the schema already says.

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 action (conditionally releases locked Escrow funds), the actor (to seller agent), and the trigger condition (EU-SWEC-CLEARED-* or compliant DDS reference). Distinguishes it from siblings like eudr_create_agent_escrow and eudr_fund_agent_escrow by being the release step.

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 condition for release is embedded in the description, implying when to use it. But there's no explicit comparison to alternatives like eudr_release_escrow_milestone or eudr_solana_settle_escrow, nor exclusions or prerequisites beyond the trigger.

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