okx_set_account_mode

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

No annotations provided. The description is minimal and does not disclose behavioral traits such as whether the operation is destructive, requires authentication, or has side effects. The admin tag hints at privilege but is 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 extremely short but at the cost of clarity. It is a single line with tags and a prerequisite, lacking structure for effective AI agent use.

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 description is woefully incomplete for a tool that changes account configuration. No output schema, no explanation of effects, no error conditions, and no context on implications of different account levels.

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%, with the parameter 'acctLv' having a description in Chinese explaining the enum values. The tool description adds no additional meaning beyond the schema, so baseline 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 only contains a Chinese tag indicating admin level and account category, and instructs to call agent_catalog first. It does not state that the tool sets the account mode (simple/margin types), relying on the parameter enum to infer functionality.

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 gives a prerequisite (call agent_catalog first) but no guidance on when to use this tool vs siblings like okx_set_leverage or okx_set_position_mode.

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