eudr_auto_slash_disputed_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 does disclose real consequences beyond the schema: autonomous on-chain execution, issuance of a BLOCKED attestation, and a full capital refund to Buyer. But it omits critical operational facts for an irreversible destructive action – required authorization/role, whether the slash can be reversed or challenged, and how failure cases are handled.

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?

It is a single front-loaded sentence with no wasted clauses: precondition, mechanism, and outcome in sequence. 'Autonomous' is mildly promotional and the sentence is dense, but nothing needs trimming.

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 high-stakes, irreversible escrow-slashing mutation with no annotations and no output schema, the description covers the outcome and side effect (attestation + refund) but not the authorization requirements, irreversibility, or post-execution state. It is adequate but under-specified for the risk profile.

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 all three parameters are already documented, which sets the baseline at 3. The description only loosely mirrors one parameter ('refunding 100% of capital' maps to slashing_penalty_pct's default of 100) and adds no format, range, or interaction detail beyond the schema.

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 states a specific verb (Executes slashing) against a specific resource (escrows) with an explicit precondition (verified deforestation violations), and names the concrete effects (EIP-712 BLOCKED attestation, 100% refund to Buyer). This is enough to distinguish it from siblings like eudr_release_agent_escrow or eudr_arbitrate_agent_escrow without opening any 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 precondition 'escrows with verified deforestation violations' (reinforced by the escrow_id schema note that the escrow must be in DISPUTED status) tells the agent when this is applicable. However, it never names an alternative or states when NOT to use it – e.g. versus arbitrate_agent_escrow or release_agent_escrow – leaving sibling selection to inference.

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