okx_get_stats_support_coin

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

No annotations are provided, so the description carries the full burden. It only conveys a read hint ([L:READ]) but discloses no behaviors such as return format, data scope, or side effects. This is insufficient for a tool with no annotations.

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 with no redundant information. It is front-loaded with tags and a prerequisite. However, it could be more informative without sacrificing conciseness.

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 set of sibling tools and lack of output schema, the description is significantly incomplete. It does not clarify what statistics are returned, for which coins, or how to interpret the output. The prerequisite to call agent_catalog implies needed context, but the tool itself is under-described.

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?

The input schema has zero parameters, so schema coverage is 100%. The description adds no parameter information, but as there are no parameters, baseline is 3. The mention of 'agent_catalog' is not parameter-related.

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 states '[L:READ] CAT:[统计]' hinting at a read operation and statistics, but fails to specify a clear verb and resource. It does not distinguish from sibling tools like okx_get_ticker or okx_get_system_status, leaving the tool's exact function ambiguous.

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 includes a prerequisite ('请先调用 agent_catalog'), providing some usage guidance. However, it does not specify when to use this tool versus alternatives, nor does it give exclusions or detailed context.

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