getMovePositionHistory

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

With no annotations, the description carries full burden. It uses 'Query' implying read-only, explains statuses (Processing, Filled, Rejected), and discloses a constraint (Max 7-day range). This provides adequate behavioral transparency for a query tool.

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?

Description is well-structured with a clear purpose, output summary, agent hint, constraint, and status meanings. Each sentence adds value without unnecessary fluff.

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 8 parameters, no output schema, and no annotations, the description covers purpose, usage, and constraints but omits details on pagination (limit, cursor) and time parameter formats. Adequate but not fully complete.

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 mentions four filter fields (category, symbol, status, blockTradeId) and implies time-range constraints, but does not describe limit, cursor, or exact format for startTime/endTime. Partial coverage adds value but not fully compensatory.

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 clearly states 'Query the history of position move (block trade) orders' with a specific verb and resource, distinguishing it from siblings like movePosition and getOrderHistory.

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 agent hint explicitly tells when to use the tool: 'Use this to check status and history of move position requests.' It also lists filterable fields, providing clear usage context, though it does not explicitly mention alternatives.

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