okx_move_positions

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

No annotations exist, so the description must disclose behavior. It only indicates it is a write operation and requires a prerequisite call, but no details about what gets modified, permissions needed, or side effects.

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 but at the cost of missing critical information. It is more under-specified than efficiently concise, as it fails to explain the tool's purpose or usage.

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?

Given no output schema and the tool's apparent complexity (moving positions), the description is completely inadequate. It omits return values, behavior, and any actionable guidance beyond a prerequisite call.

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 'body' parameter, but the description adds no additional meaning beyond what the schema already provides. Baseline 3 is appropriate as the schema carries the burden.

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 '[L:WRITE] CAT:[账户] | → 请先调用 agent_catalog' does not state what the tool does. It only tags it as a write operation and references a category, but no verb or resource is described. The tool name implies moving positions, but the description fails to clarify.

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?

No usage guidelines are provided. The instruction to call 'agent_catalog' first is ambiguous and does not explain when to use this tool versus alternatives like other position-related tools.

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