Cancel spot grid order

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

Annotations already declare destructive=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds that the operation both closes and cancels (implying position liquidation, not just order removal) and gives 'Weight: 1' for rate-limit budgeting, which is genuine value beyond the structured fields.

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?

Two short lines with no filler, though the first line is a verbatim restatement of the title, which is mild redundancy. The actual behavioral content is front-loaded and easy to parse.

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 destructive mutation tool with no output schema, the description omits what happens after cancellation (funds returned, base sold per closeSellModel, timing) and any prerequisite conditions. Schema and annotations cover the mechanics and safety hints, so this is adequate but not thorough.

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% – buOrderId, slippage, and the closeSellModel enum are fully documented in the schema. The description adds no syntax or format detail on top, so the baseline 3 applies.

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?

States a specific verb+resource: 'Close and cancel a spot grid bot order.' The 'spot grid' scope implicitly distinguishes it from pionex_bot_cancel_futures_grid_order, but the description never names that sibling explicitly, so differentiation rests on the reader parsing similar names.

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 when-to-use, when-not-to-use, or alternative guidance is offered. The only signal is the tool name itself; nothing tells the agent when to cancel a spot grid bot versus adjusting, reducing, or pausing it (all of which have siblings).

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