cancelConditionalOrder

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

Annotations include destructiveHint=true, and the description adds critical behavioral details: the dry-run safety default, the requirement for TOSSINVEST_ENABLE_CONDITIONAL_ORDERS and confirmation, and the rate limits group. This goes beyond annotation-only disclosure.

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 structured with title, explanation, rate limits, endpoint, and warning, but the sentence about tags and the warning section could be more concise. It front-loads the purpose but includes some redundancy.

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?

Lacking an output schema, the description does not explain the response format or error handling. It covers the effect (cancellation) and safety precautions, but omits return value details, which is a gap for complete agent understanding.

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 100% and schema descriptions are comprehensive for all 4 parameters. The description adds minimal extra meaning (e.g., dryRun default, confirmation requirement), but does not significantly improve understanding beyond the schema.

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 '조건주문 취소' (cancel conditional order) and explains the action using conditionalOrderId. It differentiates from sibling tools like createConditionalOrder, getConditionalOrder, modifyConditionalOrder.

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 explains the dryRun default and required environment variables for execution, but does not explicitly state when to use or avoid this tool compared to alternatives like cancelOrder for spot orders.

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