Replace Order

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

The description discloses the return message and the order status requirement. Annotations already provide destructiveHint and idempotentHint. This adds some context beyond annotations, but does not cover failure cases or side effects.

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 two sentences, front-loaded with the action and resource. Every sentence serves a purpose with no extraneous 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?

For a mutation tool with no output schema, the description covers the action, parameters, return value, and a constraint. It is fairly complete, though missing error handling details.

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 each parameter described. The description groups parameters (quantity, price, etc.) but does not add meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 open orders and lists specific parameters (quantity, price, trigger_price, trailing params). It implicitly distinguishes from siblings like cancel_order and submit_order by stating 'modify' and restricting to open/pending 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?

The description provides context by noting that only open/pending orders can be modified, but does not explicitly state when to use this tool versus canceling and resubmitting. It offers implied guidance without direct exclusions.

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