prepare_cancel_all_orders

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

With no annotations, the description carries the behavioral burden. It discloses the key non-obvious behavior: this step only returns a confirmation token, and nothing is cancelled until confirm_action. It does not cover token expiry or permissions, but the essential two-phase behavior is clear.

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?

One compact sentence conveys the step sequence, scope, return value, and deferred cancellation. There is no filler, repetition, or unnecessary detail.

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 single-parameter prepare action with no output schema, the description covers the input scope, the return value, and the required follow-up action via confirm_action. Nothing necessary for correct invocation is missing.

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 the description must compensate. It identifies the symbol as the scope of the cancellation, mapping directly to the only required parameter. For a single obvious string parameter, this is sufficient 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 states a specific verb and resource: 'cancel EVERY open order on a symbol.' It also clarifies it is only STEP 1 of 2, distinguishing it from siblings like cancel_order and confirm_action.

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?

It clearly frames when to use the tool ('STEP 1 of 2') and explains that the actual cancellation is deferred until confirm_action. It does not explicitly contrast with single-order cancellation or other cancel alternatives, so it stops short of a 5.

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