cancel_order

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

There are no annotations, and the description only repeats the core action without disclosing side effects, failure modes, or behavior when the order is not pending. The qualifier 'pending' adds minimal scope but lacks detail about cancellation semantics, idempotency, or error handling.

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 unnecessary words. The Korean translation is redundant but not harmful, and the entire description earns its place by clearly stating the tool's purpose.

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 is simple with one well-documented parameter, but as a mutating operation with no annotations or output schema, the description would benefit from stating what happens if the order is not pending or whether cancellation is idempotent. It is adequate but leaves behavioral gaps.

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 'ticket' parameter with a clear description ('Order ticket number to cancel'). The description adds no additional parameter semantics, so the baseline of 3 is appropriate given full schema coverage.

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 ('Cancel') and resource ('a pending order'), clearly stating the tool's action. It differentiates from sibling tools such as open_order, modify_order, and close_position by specifying cancellation of pending 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?

No guidance is provided on when to use this tool versus alternatives like modify_order or close_position. The description does not mention prerequisites, exclusions, or context for choosing this tool.

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