cancel_order

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

With no annotations provided, the description carries the full burden. It discloses that execution is immediate and that it reduces exposure, which are meaningful behavioral traits. However, it does not mention potential side effects (e.g., if the order is already filled) or permission requirements, leaving some gaps in transparency.

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 two short sentences with no redundant information. The Korean translation is a helpful addition, and every word contributes to clarity. It is concise 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?

For a simple cancellation tool, the description covers the core purpose and execution behavior. It lacks a note about error cases (e.g., attempting to cancel a non-existent or already-filled order), but given the simplicity and complete schema, it is sufficiently complete.

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 already provides 100% coverage with descriptions for both parameters, including the fallback for account_id. The description adds no additional parameter-level information, so it meets the schema-coverage baseline without exceeding it.

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 ('Cancel') and resource ('an open order'), and adds the Korean translation for clarity. It clearly distinguishes from sibling tools like modify_order and create_order by focusing on cancellation. The added phrase 'reduces exposure' gives extra context about the tool's effect.

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 implies when to use the tool by specifying 'open order', which excludes filled or canceled orders. It does not explicitly mention alternatives or when not to use it, but the context is clear enough for an agent to select this tool for cancellation tasks.

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