okx_get_lead_trader_history

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

No annotations are provided, so the description carries the full behavioral burden. It includes a custom read-only tag '[L:READ]', which is helpful for safety, but it does not disclose other traits such as authentication requirements, rate limits, or any side effects (e.g., data freshness).

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 lines) but under-specifies the tool's purpose and behavior. While it is concise, it sacrifices completeness for brevity. It could benefit from a clear sentence about what the tool does.

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?

With 3 parameters, no output schema, and no annotations, the description does not adequately explain the tool's return values, parameter behavior, or typical usage. The prerequisite hint is useful but insufficient for an agent to invoke this tool correctly.

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%, so the input schema documents all three parameters. The description adds no additional parameter context beyond what is already in the schema. The baseline of 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 hints at a read operation related to copy trading via the tag '[L:READ] CAT:[策略-跟单]', but does not explicitly state that the tool retrieves lead trader history. The name 'okx_get_lead_trader_history' is clear, but the description lacks a direct verb+resource 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 only provides a prerequisite ('请先调用 agent_catalog') but offers no guidance on when to use this tool versus alternatives like okx_get_lead_trader_positions or okx_get_lead_trader_stats. There is no when/why context.

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