orders_update_order

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

No annotations are provided, so the description carries the full burden. It states that it updates mutable fields, but gives no details on side effects, permission requirements, partial-update behavior, or whether changes are reversible. The word 'update' implies mutation, but little else is disclosed.

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?

A single, front-loaded sentence that conveys the purpose and examples without filler. It is efficiently structured and immediately understandable.

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?

The tool is simple with fully described schema parameters. However, with no annotations and no output schema, the description is minimal. It does not clarify whether the update is partial (only provided fields are changed) or what the response looks like. Adequate but not comprehensive.

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?

The input schema already describes all three parameters with 100% coverage. The description's mention of 'shipping address' and 'internal notes' reinforces the schema but adds no new semantics about parameter formatting, constraints, or relationships. Baseline 3 for full coverage 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 identifies the action ('Update'), the target resource ('an existing order'), and the scope ('mutable fields'), with concrete examples (shipping address, internal notes). This distinguishes it from sibling tools like create, cancel, refund, and track 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 usage context is implied: use when modifying an order's mutable fields. However, it does not explicitly state when not to use it or mention alternatives such as canceling, refunding, or listing orders. It does not provide exclusion criteria or direct comparisons.

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