okx_transfer

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

No annotations are provided, so the description must disclose behavioral traits. It merely contains [L:WRITE] hinting at a write operation but does not mention authorization needs, rate limits, what happens during the transfer (e.g., if funds are deducted immediately), or any side effects. The description is insufficient for an agent to understand the tool's behavior.

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 (one line), which is concise but at the expense of clarity. It uses brackets and arrow notation that may be cryptic. It is structured but lacks explanatory power.

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 complexity of a transfer tool with four required parameters and no output schema, the description is far from complete. It omits what to do after the transfer, how to check status, and does not reference any sibling tools. The prerequisite to call agent_catalog is present but insufficient.

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 covers all four parameters with descriptions and enums for from/to, so baseline is 3. The description adds no additional meaning beyond what the schema already provides, but it does not detract either.

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 name 'okx_transfer' clearly indicates a transfer operation, and the schema parameters (from/to account codes) reinforce that it transfers funds between accounts. The description includes CAT:[资金] which means 'funds' in Chinese, adding a category hint. However, the description does not explicitly state the purpose in plain language, relying on the name and schema.

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' or 'please call agent_catalog first') but does not explain when to use this tool versus alternatives like okx_get_transfer_state or okx_transfer_subaccount. No guidance on when not to use it or in which scenarios it is appropriate.

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