okx_get_taker_volume_contract

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

No annotations exist, yet the description provides no behavioral context such as rate limits, authentication, or side effects. The label '[L:READ]' hints at a read operation but is insufficient and not explicitly explained.

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 not well-structured. It mixes metadata and a prerequisite note without a clear statement of purpose. While concise, it lacks clarity and proper organization.

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 complexity and lack of output schema, the description is severely incomplete. It does not explain what the tool returns, how to interpret results, or any constraints beyond schema parameters.

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 Chinese descriptions for both parameters (ccy and instId). The description adds no additional meaning beyond what the schema already provides, so 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 uses cryptic labels like '[L:READ]' and 'CAT:[统计]' without explicitly stating that the tool retrieves taker volume for contracts. The name implies the function but the description fails to clarify it 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?

No guidance on when to use this tool versus sibling tools like 'okx_get_taker_volume' or 'okx_get_contracts_taker_volume'. The prerequisite 'call agent_catalog' suggests documentation but does not provide direct comparison.

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