okx_get_subaccount_list

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

With no annotations provided, the description carries the full burden. The '[L:READ]' tag hints at read-only behavior, but there is no disclosure of side effects, authentication requirements, error conditions, or output format. Behavioral traits are largely absent.

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 uses non-standard markers and Chinese text that may reduce clarity for an English-speaking AI agent. While concise, it lacks clear structure and readable sentences.

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 has one optional parameter, no output schema, and no annotations. The description does not explain return values, and the prerequisite instruction is vague. It leaves significant gaps for an agent to understand the tool's full context.

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 description coverage is 100% for the single optional boolean parameter. The description adds no extra meaning beyond the schema, so baseline 3 is justified.

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 does not explicitly state the tool's purpose; it uses cryptic tags like '[L:READ]' and 'CAT:[账户-子账户]' and a Chinese instruction to call agent_catalog first, leaving the actual function to be inferred from the tool name. It relies on the name 'get_subaccount_list' to convey meaning.

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 only provides a single instruction to call agent_catalog first, which is a prerequisite. It lacks guidance on when to use this tool versus sibling tools like okx_list_subaccounts or okx_get_subaccount_balance, and does not indicate when not to use it.

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