create_order

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

No annotations are provided, so the description must disclose behavioral traits. It clearly warns '실제 주문이 접수됩니다' (actual order is placed) and specifies the requirement for `confirmHighValueOrder` for large orders. It could mention other behaviors like rate limits or reversibility, but the warning is sufficient for a creation tool.

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 short, front-loaded with the core purpose, and uses bullet-point-like structure with an emoji warning. Every sentence adds necessary information without 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?

Given the tool has 10 parameters and no output schema, the description covers the essential behavioral aspects (real order, parameter choice, high-value confirmation). It does not explain return values or error cases, but the schema handles parameter details. For a complex trading tool, it is adequately 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?

Schema coverage is 100%, so baseline is 3. The description adds value by explicitly stating the choice between `quantity` and `orderAmount` (US market only) and the need for `confirmHighValueOrder` for orders over 100 million won. This clarifies usage beyond what the schema provides.

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 '주문 생성 (매수/매도)' meaning 'Create order (buy/sell)', which is a specific verb and resource. It also mentions parameter selection and a high-value warning, distinguishing it from siblings like `create_conditional_order`. The purpose is unmistakable.

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 advises using either quantity-based or amount-based entry and notes the high-value flag. However, it does not explicitly contrast this tool with alternatives like `create_conditional_order` or when to use LIMIT vs MARKET. The guidance is clear for common cases but lacks comprehensive 'when to use' context.

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