create_htlc

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

No annotations provided. Description mentions idempotency via client_request_id but does not detail side effects, error states, or what happens on failure. The tool's impact on state machine is implied but not fully explained.

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?

Concise and well-structured: main purpose, usage guidance, then parameter notes. No redundant information, each sentence adds value.

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?

No output schema. Description explains purpose and param notes but lacks details on return value, error handling, or how this tool fits into the overall trade lifecycle. Could be more complete for a complex settlement tool.

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%, baseline 3. Description adds value with notes on role requirements, txHash format, and chainType defaults, clarifying usage beyond schema definitions.

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?

Description clearly states the tool's purpose: recording the on-chain HTLC lock tx hash to advance settlement, with DVP guarantee. Differentiates from siblings like refund_htlc and withdraw_htlc by focusing on the lock step.

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?

Explicit USE WHEN and DO NOT USE WHEN conditions, specifying the prerequisite (trade accepted, lock tx broadcast). Provides clear context for correct invocation.

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