okx_copy_trader

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

With no annotations, the description carries the full burden. It only notes '[L:WRITE]' implying a mutation, but does not disclose what changes occur (e.g., initiates copy trading, modifies settings), side effects, or required permissions. No behavioral details beyond the write indicator.

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), making it concise, but it sacrifices clarity with cryptic labels and no structure. It is minimally adequate but not well-organized.

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 has 4 parameters, no output schema, and no annotations, the description is insufficient. It omits the overall action, return value, and usage context, only providing a prerequisite and category. Incomplete for effective invocation.

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 clear Chinese descriptions for parameters (e.g., '跟单数量', '产品类型'). The tool description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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 a category label '[策略-跟单]' and an action label '[L:WRITE]' but fails to state a specific action verb. It is vague about what the tool actually does, only hinting at copy trading. The name and schema suggest copying a trader, but the description lacks a clear purpose statement.

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 includes a prerequisite to call 'agent_catalog' first, but does not explain when to use this tool versus alternatives, when not to use it, or how it differs from sibling copy trading tools like 'okx_stop_copy_trader' or 'okx_set_copy_settings'. No usage context provided.

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