modify_order

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

The warning indicates destructive behavior but lacks details on side effects, restrictions, or permissions. No annotations are provided, so the description carries full burden, which it does not fulfill beyond the basic warning.

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 very short and front-loaded but omits necessary usage guidelines and behavioral details. It could be slightly expanded without losing conciseness.

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 (6 parameters, conditional requirements, no output schema), the description is too minimal. It lacks information on what happens after modification, account handling, and relationship to sibling tools.

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 description coverage is 100%, so the description adds no extra parameter meaning beyond the schema. Baseline score of 3 is appropriate as it does not enhance understanding of parameter semantics.

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 an existing order by changing price or quantity, distinguishing it from sibling tools like cancel_order and create_order. The warning about actual order change reinforces its purpose.

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?

No explicit guidance on when to use this tool vs alternatives such as cancel_order or modify_conditional_order. The description only says 'modify order' without context about the specific scenarios that warrant its use.

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