movePosition

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

No annotations provided, but description discloses fee-free nature, price constraints, leg limit, and processing status. Does not discuss idempotency, reversibility, or exact response fields, but adequately covers key behavioral traits.

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?

Three well-organized paragraphs with front-loaded main action, followed by constraints and hint. No fluff, but could be slightly more concise by merging repetitive points. Generally effective.

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?

Covers prerequisites, constraints, and post-action hint, but lacks explanation of response format. Without output schema, the description should detail what the agent can expect upon success or processing. Adequate but with 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?

Schema coverage is 0%, so description must compensate. It adds context for the list parameter (legs, price range) but does not explicitly define fromUid, toUid, or list structure. Incomplete parameter guidance.

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?

Description clearly states 'Transfer positions between two unified trading accounts (UIDs) without fees.' Specifies verb, resource, and key condition. Distinguishes from siblings like getMovePositionHistory by focusing on execution.

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?

Provides explicit hint for sub-account movement, required master API key, mode requirements (UTA, one-way mode), max legs (25), price range (95%-105%), and follow-up action (check getMovePositionHistory). Covers when to use and constraints.

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