Cancel every open perpetual order on HyperLiquid at once, clearing pending entries and exits so you can reset or adjust your trading strategy quickly.
Cancel all open perp orders on HyperLiquid.
| Name | Required | Description | Default |
|---|---|---|---|
| apiKey | Yes | GDEX API key for AES encryption | |
| walletAddress | Yes | Control wallet address | |
| sessionPrivateKey | Yes | Session private key from sign-in |
Changes observed during successful MCP inspections.
v4.11.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With zero annotations, the description carries the full burden of behavioral disclosure for a destructive mutation, yet it only restates the action. It says nothing about irreversibility, required auth/permissions, scope (all symbols/dexes?), rate limits, or whether it can be undone.
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?
A single front-loaded sentence with no wasted words. It is tight and well-structured, though the brevity reflects under-specification rather than deliberate economy.
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 all-cancel operation with no annotations and no output schema, one sentence is insufficient. It omits safety, auth, and scope details an agent needs before invoking it.
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% and all three credentials are documented in the schema, so the baseline is 3. The description adds no parameter meaning beyond what the schema already provides.
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 and resource ('Cancel all open perp orders') with a clear platform scope ('on HyperLiquid'). The word 'all' implicitly distinguishes it from the singular sibling cancel_perp_order, though no sibling is named explicitly.
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 gives no when-to-use guidance, no prerequisites, and never mentions the alternative cancel_perp_order or close_all_positions. An agent must infer the use case entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.