cancelOrder

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

Discloses important behavior: response is acknowledgment only, confirmation via WebSocket stream. No annotations exist, so description carries full burden. Does not mention rate limits or auth, but these are typical for a cancel endpoint.

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?

Reasonably concise with bullet points and hints. Some redundancy between agent hint and bullet points, but overall well-structured and front-loaded.

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 key aspects: action, required parameters, behavior, and special case (TradFi). Lacks error handling details, but for a simple cancel tool this is sufficient given no output schema.

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?

With 0% schema description coverage, the description adds significant meaning: explains the relationship between orderId and orderLinkId, priority rule, and orderFilter usage. Does not detail category or symbol but provides enough context.

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 the tool cancels a single open order by orderId or orderLinkId. It differentiates from siblings like batchCancelOrders and cancelAllOrders by specifying 'single open 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?

Provides clear when-to-use: cancel a single open order. Includes constraints (must provide orderId or orderLinkId, priority rule, orderFilter for spot) and a TradFi hint for category. Lacks explicit alternatives but siblings imply batch/available.

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