okx_get_contract_position_trader_ratio

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

The '[L:READ]' hint indicates read-only, but with no annotations and no further detail, the description fails to disclose critical behavioral traits like return format, data scope, or potential side effects.

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 its brevity stems from omission of useful information rather than efficient communication. It is not verbose, but it is under-informative.

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 no output schema and many sibling tools, the description is too sparse. It does not explain the return value or how it differs from similar contract ratio tools, leaving the agent under-informed.

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% (one parameter, well-described). The description adds no additional meaning, so it meets the baseline expectation without compensation.

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 only categorizes the tool as 'statistics' and instructs to call agent_catalog first. It does not clearly state what 'contract position trader ratio' means or what action the tool performs, leaving its purpose vague.

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 a prerequisite (call agent_catalog first) but gives no guidance on when to use this tool versus its many siblings, such as okx_get_long_short_ratio or okx_get_top_trader_long_short_ratio.

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