okx_get_subaccount_balance

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only behavior, authentication requirements, or rate limits. The READ tag is non-standard and insufficient.

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 poorly structured for an English-speaking AI. It mixes tags, Chinese text, and a prerequisite note without clear formatting. The information is dense but not effectively communicated.

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?

The tool is a simple balance query, but the description lacks information about return format, error handling, or any output. The prerequisite is noted but not explained. No output schema exists, so more context is needed.

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% for the single parameter 'subAcct', and the schema description (Chinese) defines its purpose. The tool description adds no further meaning, so the baseline score of 3 applies.

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 mostly in Chinese and does not clearly state its purpose in English. It includes a READ tag and a category, but the function is only implied by the tool name. The prerequisite note '请先调用 agent_catalog' adds confusion rather than clarity.

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 mentions a prerequisite ('call agent_catalog first') but provides no guidance on when to use this tool versus siblings, such as okx_get_subaccount_trading_balance or okx_get_balance. No exclusions or alternatives are given.

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