kis_revise_or_cancel_domestic_order

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

The description discloses that only unexecuted orders can be revised/canceled, and executed orders cannot be canceled. With no annotations, this adds value, but it lacks details on side effects, idempotency, or rate limits, which are important for a mutation 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?

Two short sentences, no wasted words. The action (revise or cancel) is front-loaded, making it efficient for an agent to parse quickly.

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 tool with 11 parameters and no output schema, the description is too minimal. It lacks context on required fields, what org_order_orgno refers to, success/failure behavior, and prerequisites. More completeness is needed for safe use.

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% with all parameters described in Korean, so baseline is 3. The description itself adds no extra meaning beyond what the schema already 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 it revises or cancels unexecuted domestic stock orders, using specific verbs 'revise' and 'cancel' with the resource 'domestic orders'. It distinguishes from sibling tools like kis_place_domestic_order (which places new orders) and kis_get_* (which read data).

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 usage for unexecuted orders but does not explicitly state when to use this tool versus alternatives. No 'when not to use' or alternative tool names are provided, leaving the agent to infer context.

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