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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is partly covered. The description adds important behavior beyond that: it returns an unsigned transaction, never broadcasts, and warns to scope any eventual signature to the exact returned chain, contract, calldata, and value.

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 front-loaded, using one sentence for purpose and broadcast behavior, one compact list for valid actions, and one sentence for the signature-scoping caution. Every sentence adds useful information without padding.

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?

The description covers the tool's purpose, valid actions, non-broadcast behavior, and signature safety, which are the most critical points. However, for a six-parameter transaction-preparation tool with no output schema and no schema descriptions, the absence of guidance on how the other parameters map to specific actions leaves meaningful gaps.

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 0%, so the description must carry parameter meaning, but it only enumerates values for the 'action' parameter. It leaves case_id, chain_id, contract, commitment, and receiver_award_atomic undocumented, which is a major gap for a six-parameter tool.

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 ('Simulate'), resource ('case action'), and return artifact ('unsigned wallet transaction'), and immediately clarifies 'Never broadcasts.' This distinguishes it from sibling preparation tools that target payments or donations.

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 gives clear usage context: it is for simulating and preparing an escrow case action without broadcasting. The full action list further clarifies intended invocation, but no explicit exclusions or sibling alternatives are named.

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