eudr_solana_settle_escrow

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that this is a sub-second Solana payout in SPL-USDC conditioned on an Ed25519 EUDR attestation, but it omits critical financial-operation details such as required authorization, irreversibility, fee behavior, failure modes, and confirmation semantics. The condition is helpful context, but the safety and execution profile remains underspecified.

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 dense sentence with no filler and the key operational facts are front-loaded. Every clause earns its place by specifying the action, payout model, chain, asset, speed, and condition. It is appropriately sized for such a capability.

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?

This is a complex financial settlement tool with seven parameters, no annotations, and no output schema. While the schema covers parameter descriptions, the description does not explain return behavior, confirmation, authorization needs, or failure outcomes, which an agent would need before invoking a real-value escrow payout. For a mutation/settlement operation, the definition is not complete enough.

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 seven parameters, including job_id, buyer_wallet, and recipients. The description adds conceptual context about recipients being smallholders and cooperatives and about SPL-USDC settlement, but it does not add syntax, constraints, or format details beyond what the schema provides. Baseline 3 is appropriate when the schema does the parameter-level work.

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 names a specific verb, resource, chain, asset, payout model, and condition: executes a Direct Split escrow payout on Solana Mainnet in SPL-USDC conditioned on an Ed25519 attestation. This distinguishes it from generic escrow siblings and from Solana pay-link or agent micropayment tools. An agent can identify its core purpose without opening the schema.

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 implies when the tool applies: Solana Mainnet SPL-USDC settlement conditioned on physical truth attestation. However, it does not explicitly compare against nearby escrow siblings such as eudr_release_escrow_milestone, eudr_create_milestone_escrow, or eudr_agent_micro_pay, nor does it state when not to use it. Usage is therefore inferable but not well-routed.

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