edit_order

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

The description gives minimal behavioral insight. It implies the order is modified but does not specify if updates are partial or full, whether the order must be in a specific state, or any side effects. Since no annotations are provided, the description carries the full burden, which it fails to meet.

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 a single sentence with no extraneous information, making it concise. However, the extreme brevity may sacrifice necessary detail, but for a simple edit tool, it is appropriately sized.

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?

With no output schema and no annotations, the description is insufficient. It does not explain the return value, whether the edit is successful, or any postconditions. For a mutation tool, more context is needed.

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 input schema already explains each parameter (order_id, order_price, order_quantity). The description adds no additional semantic meaning beyond the schema, making it adequate but not enhanced.

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 'Edit an existing order' clearly states the verb (edit) and resource (order), distinguishing it from sibling tools like create_order or cancel_order. However, it lacks any specificity about which fields can be edited or constraints.

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 guidance is provided on when to use this tool versus alternatives like edit_algo_order or cancel_order. There is no mention of prerequisites, order state requirements, or suggested contexts.

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