withdraw_htlc

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

Reveals that revealing the preimage makes the swap atomic and simultaneously unlocks the counterparty leg. Lacks mention of irrevocability or on-chain txHash requirement, but sufficient for the 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?

Compact description with clear structure: one-line summary, use/don't-use section, and param notes. Every sentence provides necessary information.

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?

Covers purpose, usage, and key parameters adequately. No output schema, but for a claim operation, missing return value info is acceptable given the straightforward nature.

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 baseline is 3. Adds value by specifying preimage format (0x-prefixed 32-byte hex) and chainType for non-EVM legs beyond schema descriptions.

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?

Clearly describes the tool as an atomic claim that reveals the preimage to unlock both legs. Distinguishes from sibling 'refund_htlc' by mentioning timelock expiry.

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?

Explicitly states when to use and when not to use, including a specific alternative tool (refund_htlc) for expired timelocks.

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