okx_get_top_trader_long_short_ratio

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. The '[L:READ]' tag implies read-only, but no details on rate limits, authorization needs, or side effects are given. The description does not add substantial behavioral context beyond the inferred safe read.

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 it is under-specified rather than concise. The instruction to call agent_catalog first is a necessary dependency hint, but the description lacks substantive content. It could be more informative without adding length.

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's moderate complexity (contract ID, time range), no output schema, and no annotations, the description should explain return value format and behavior. It only provides a minimal category tag and a prerequisite, leaving significant gaps.

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%, with clear parameter descriptions (e.g., instId, begin, end as milliseconds). The description adds no additional meaning to the parameters, 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 'CAT:[统计]' hints at a statistics category but does not explicitly state the tool's purpose (e.g., 'Get top trader long/short ratio for a contract'). It is not a tautology but remains vague, and fails to distinguish from many similar sibling tools like okx_get_long_short_ratio.

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 provides no guidance on when to use this tool versus alternatives. The instruction '→ 请先调用 agent_catalog' is a prerequisite, not usage context or exclusion criteria. Missing when-not-to-use and alternative tool references.

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