okx_list_subaccounts

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

With no annotations, the description must fully disclose behavior. The '[L:READ]' hint indicates a read operation, but it lacks details on authentication, side effects, or other behavioral traits. This is insufficient for a tool with no annotation support.

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 concise, using a single line with structured metadata. However, the use of brackets and Chinese may obscure meaning slightly. It is efficient but could be clearer.

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?

For a simple one-parameter list tool with no output schema, the description combined with schema is mostly adequate. However, it lacks explanation of return format and why the prerequisite 'agent_catalog' is necessary, leaving some gaps.

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 100% coverage for the single optional 'enable' parameter, and the description does not add additional meaning beyond the schema. Remains at baseline.

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 tool name directly indicates listing subaccounts, and the description adds a '[L:READ]' label and a category, but the Chinese text and bracket format may reduce clarity for some users. It is not a tautology and conveys purpose.

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 instruction '请先调用 agent_catalog' (call agent_catalog first), giving some guidance on when to use. However, it does not clarify alternatives or when not to use this tool versus siblings like okx_get_subaccount_list.

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