Cancel Order

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

Annotations already declare destructiveHint: true, so the agent knows it's destructive. The description adds the crucial behavioral context that LIVE writes require SAXO_ENABLE_LIVE_TRADING=true, which goes beyond annotations.

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 concise sentence that front-loads the core function, but it could be slightly more structured, e.g., by separating the cancellation from the environment constraint.

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?

Given the sibling tools for canceling multileg orders (saxo_cancel_multileg_order) and no output schema, the description adequately covers the tool's purpose and key constraint, though it could mention error handling or side effects.

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 has 0% description coverage, yet the description offers no explanation of what 'orderIds' or 'accountKey' represent, failing to compensate for the schema's lack of semantic meaning.

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 action 'Cancel' and the resource 'working orders,' which is specific and distinguishes from sibling tools like saxo_cancel_multileg_order that target multileg orders.

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 mentions an environment variable requirement for LIVE writes but does not provide explicit when-to-use or when-not-to-use guidance against alternatives like saxo_cancel_multileg_order.

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