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

With no annotations, the description carries the behavioral disclosure burden. It is transparent that this only prepares an unsigned payload, not a signed submission, and that a claimant wallet signature is required. It could add more detail about return format or failure conditions, but the core behavior is clearly disclosed.

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 sentences communicate the action, the resource, the eligibility context, and a required precondition with no filler. The key operational fact that the payload is unsigned is front-loaded.

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 simple two-parameter tool with no output schema, the description is largely complete. It identifies the contract, the purpose, and the signing requirement. Minor details such as chain/network context or what the payload format is are absent but not essential for correct invocation.

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 both parameters well. The tool description adds only contextual framing ('eligible escrow refund', 'claimant wallet signature') rather than new parameter-specific semantics, which fits the baseline of 3 when the schema handles parameter documentation.

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 action ('prepare an unsigned transaction payload'), a target resource ('Escrow contract'), and the purpose ('claim an eligible escrow refund'). It is clearly distinct from all sibling tools, which concern domains and marketplace operations rather than escrow claims.

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 clearly states the context in which the tool is used: preparing a refund claim for an eligible claimant. It also gives a key prerequisite, the claimant wallet signature. It does not explicitly name alternatives or when-not-to-use it, but the sibling set makes the intended use obvious.

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