amend_order

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

Discloses critical behavior: collateral is adjusted automatically (extra funds sent or refunded) when value changes. No annotations are provided, so the description fully covers the behavioral traits.

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?

Three concise, well-structured sentences. Front-loaded with the core action, then efficiency benefit, then constraint, then collateral behavior. No wasted words.

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 no output schema and 5 parameters, the description covers all essential information: purpose, constraints, parameter details, and behavioral side effects. An agent can correctly invoke the tool.

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?

All parameters are already described in the schema, but the description adds contextual details like microunits for price/quantity and default slippage, enhancing understanding beyond the 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 edits an unfilled order in-place, specifying the modifiable fields (price, quantity, slippage). It distinguishes itself from the alternative cancel+recreate approach, making the purpose unambiguous.

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?

Explicitly states it is faster and cheaper than cancel+recreate, and that it only works on orders with zero filled quantity. Provides clear context for when to use this tool versus alternatives.

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