okx_get_public_lead_trader_pnl

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

With no annotations provided, the description must disclose behavioral traits. It only includes a read hint ([L:READ]) but lacks details on what the tool actually returns, any side effects, or required permissions. This is insufficient for a mutation-aware tool.

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 but lacks clarity. It uses a tag-based format and Chinese, which may confuse agents. While it is brief, it is not effectively concise because the content is incomplete and unclear.

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 two required parameters and no output schema, the description should explain the return format or data structure. It does not, leaving the agent with insufficient context to use the 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 description coverage is 100%; both 'uniqueCode' and 'lastDays' are described adequately in the schema. The description adds no additional meaning beyond what is already in the schema, so a baseline score 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 does not explicitly state the tool's function; it uses cryptic tags (L:READ, CAT) and Chinese text. The purpose is only inferrable from the tool name 'okx_get_public_lead_trader_pnl', which is not ideal for an AI agent.

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 suggests a prerequisite ('请先调用 agent_catalog') but provides no guidance on when to use this tool versus alternatives like 'okx_get_public_lead_traders' or 'okx_get_lead_trader_stats'. No comparative context is given.

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