okx_create_subaccount

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 indicates a write operation ('[L:WRITE]'), but does not disclose behavioral traits such as authentication requirements, side effects, rate limits, or what exactly is created. The description lacks sufficient detail.

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 cryptic, using non-standard abbreviations and a reference to another tool. While concise, it sacrifices clarity and does not front-load useful information. The structure is not helpful for an AI agent.

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 creation tool with many sibling subaccount tools, the description is incomplete. It does not explain return values, prerequisites beyond calling agent_catalog, or what happens after creation. Without an output schema, the tool's behavior is under-specified.

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 with Chinese descriptions for both parameters: 'subAcct' (required, subaccount name) and 'label' (remark). The description adds no additional meaning beyond the schema. With high coverage, baseline score 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 is cryptic, using Chinese tags like '[L:WRITE]' and 'CAT:[账户-子账户]', and directs to call agent_catalog first. It does not clearly state that it creates a subaccount, relying on the tool name for inference. The purpose is barely conveyed.

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 ('请先调用 agent_catalog'), which provides some guidance on when to use this tool. However, it does not differentiate from sibling subaccount-related tools (e.g., okx_list_subaccounts, okx_get_subaccount_balance) or specify 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.