Cancel every open order in one action. Use with caution, as this removes all pending orders and returns the number of cancelled orders.
Cancel all open orders.
Use with caution - this will cancel ALL pending orders.
Returns count of cancelled orders.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It warns 'Use with caution,' explicitly states that ALL pending orders will be cancelled, and discloses the return value as a count. This is strong behavioral disclosure for a destructive bulk operation, though it does not explicitly discuss irreversibility or side effects beyond cancellation.
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 short sentences: the action, a caution, and the return value. Every sentence earns its place, and the warning is front-loaded where it matters.
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 zero-parameter tool with an output schema present, the description provides the necessary scope, caution, and outcome. Nothing essential is missing for an agent to decide whether to invoke it and what to expect.
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?
The tool has zero parameters, so there is no parameter documentation burden. The schema coverage is vacuously complete, and the description appropriately adds no parameter details.
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 states a specific verb ('Cancel') and resource ('all open orders'), and reinforces the scope with 'ALL pending orders.' This clearly distinguishes it from the singular sibling cancel_order.
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 makes the usage context unmistakable: use this when you want to cancel every open order. It does not explicitly name cancel_order as the alternative for single-order cancellation, but the all-encompassing scope is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.