modifyOrder

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

Extensive behavioral context beyond annotations: dryRun default, confirmation requirement, market-specific rules (KR quantity required, US quantity not allowed), rate limits group, and specific error codes. No contradictions with annotations (destructiveHint=true, readOnlyHint=false).

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?

Concise and well-structured with clear sections for KR stocks, US stocks, and important warnings. No unnecessary sentences; every part adds information.

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?

No output schema, so description should cover return behavior. It provides many error codes and prerequisites, but does not describe the success response format. Still, it is comprehensive enough for safe invocation.

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%, baseline 3. Description adds value by summarizing market-specific parameter constraints (KR vs US) and mentioning the rate limits group, which is not in the schema. It also provides context for dryRun and confirmation, though these are already in 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 the tool modifies existing orders (price or quantity) and differentiates between KR and US markets. It distinguishes itself from sibling tools like createOrder or cancelOrder by specifying its action on existing 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?

Usage is implied for modifying orders, but no explicit comparison to alternatives like cancelOrder. However, it provides critical guidelines: default dryRun=true, requirement of TOSSINVEST_ENABLE_TRADING=true and confirmation for actual execution, and market-specific constraints, which are highly useful for correct usage.

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