okx_withdrawal_lightning

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

No annotations are provided, and the description does not disclose behavioral traits such as irreversibility, fees, success/failure outcomes, or required permissions. For a financial action tool, this is insufficient.

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 very short (two elements), but it is not front-loaded with purpose. The directive to call agent_catalog takes precedence, which is not the primary purpose.

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?

Given the tool is a withdrawal action with no output schema and no annotations, the description should explain behavior, risks, and return values. It only provides a category and a prerequisite, leaving significant 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 100% with Chinese descriptions for all three parameters (ccy, amt, to). The description adds no additional meaning beyond the schema, but the schema itself is adequate.

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 uses '[L:FUND_TRANSFER]' to suggest a fund transfer category, but does not explicitly state that the tool is for withdrawing funds via Lightning Network. The main content is a directive to call agent_catalog first, leaving the tool's purpose vague.

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 mentions a prerequisite (call agent_catalog) but provides no guidance on when to use this tool versus alternatives like the standard okx_withdrawal tool. There are no exclusions or comparisons.

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