createOrder

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

Annotations include destructiveHint=true and openWorldHint=true. Description adds that it affects real assets, dryRun default is true, and confirmation is required for actual execution. Also mentions rate limits and error conditions beyond what annotations provide.

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?

Description is well-structured with sections, bullet points, and warnings. It front-loads the purpose. Slightly verbose but each sentence adds value; could be trimmed slightly without loss.

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 complexity (multiple modes, constraints, no output schema), the description covers usage, parameters, and safety warnings well. Missing return value explanation, but the schema is comprehensive and sibling tools for further details exist.

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%, so baseline is 3. Description adds value by summarizing the two order creation methods (quantity-based vs amount-based) and their differences, which helps the agent choose correctly.

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 '주문 생성' and '매수 또는 매도 주문을 생성합니다.' which clearly indicates the verb (create) and resource (orders). It distinguishes from sibling tools like 'cancelOrder' and 'modifyOrder' by being the primary order creation endpoint.

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?

Provides explicit guidance on when to use 'quantity' vs 'orderAmount', constraints on orderAmount (US MARKET only, regular hours), and mentions dryRun and confirmation requirements. Does not explicitly state when not to use this tool but context is clear from sibling names.

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