okx_convert_trade

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

With no annotations, the description carries full burden but only conveys that it is a write operation ('[L:WRITE]'). It fails to disclose critical behavioral traits such as order type (market/limit), whether it executes immediately, required permissions, or potential side effects like affecting balances.

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?

While short, the description is under-specified rather than concise. It lacks essential information, making it unhelpful. Every sentence should add value, but here the single line does not adequately summarize the tool's function.

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 that there is no output schema and the tool performs a complex action (trade), the description should explain expected return values or confirmations. It does not address what the agent should expect after invocation, leaving significant gaps for a trading operation.

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?

The input schema has 100% description coverage, so the schema already documents the three parameters (sz, toCcy, fromCcy) clearly. The description adds no additional semantic value beyond what the schema provides, warranting the baseline score of 3.

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 is vague; '[L:WRITE] CAT:[账户]' does not clearly state that the tool performs a currency conversion trade. The schema implies conversion, but the purpose is not explicitly articulated, barely distinguishing it from sibling convert tools like okx_convert_contract_coin or okx_convert_currency_pair.

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 only provides a prerequisite ('请先调用 agent_catalog') but no guidance on when to use this tool versus alternatives such as okx_get_convert_estimate_quote or okx_get_convert_currencies. It lacks explicit when-to-use or when-not-to-use context.

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