okx_get_contract_trader_ls_ratio

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

No annotations are provided, and the description offers minimal behavioral info beyond a read hint. It does not disclose side effects, authorization needs, or data scope, leaving the agent without critical context for a data-retrieval 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 extremely short but not effectively concise—it omits essential purpose and usage information. The structure (bracket prefix and prerequisite) is not front-loaded with the tool's main function.

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 large number of similar sibling tools and the lack of an output schema, the description is severely incomplete. It fails to explain what data is returned, how it differs from related tools, or how to use the parameters effectively.

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 descriptions for all three parameters (end, begin, instId). The description adds no extra parameter context 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 is vague: '[L:READ] CAT:[统计] | → 请先调用 agent_catalog' does not explicitly state that the tool retrieves the contract trader long-short ratio. The purpose must be inferred from the tool name. No clear verb or resource is described.

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 instructs to call agent_catalog first, but provides no guidance on when to use this tool over its many siblings (e.g., okx_get_long_short_ratio, okx_get_top_trader_long_short_ratio). No context for selection is given.

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