kraken_cancel_all_orders_after

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

No annotations are provided, so the description carries the full burden. It discloses the key behavior (automatic cancellation after a time window) but does not mention whether the scheduled cancellation can be modified, whether it is a one-time action, or any safety implications. This is a destructive operation, so more context would be valuable.

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?

The description is a single, front-loaded sentence with no redundant words. Every word contributes to explaining the tool's core function.

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?

The tool has low complexity (one required parameter) and an output schema, so the description does not need to explain return values. The description adequately explains the tool's purpose, though it could be slightly more complete by specifying whether the cancellation is a one-time event or if the timeout applies globally to all open orders.

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 input schema fully documents the single 'timeout' parameter, including its type, minimum, and description. The tool description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 uses a specific verb ('schedule') and resource ('all open orders') with a clear time-window scope. It distinguishes itself from sibling tool 'kraken_cancel_all_orders' by indicating a delayed cancellation rather than an immediate one.

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 clearly implies usage for delayed cancellation, and the sibling tool name 'kraken_cancel_all_orders' provides a contrast. However, it does not explicitly state when not to use this tool or mention alternative tools.

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