update_order

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

With no annotations, the description carries full responsibility for behavioral disclosure. It does not explain whether updates are partial or full, whether tags are replaced or merged, or any side effects. The mutation is implied but insufficiently detailed for an agent to predict the outcome confidently.

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 core action and resource, followed by a precise exclusion. Every word earns its place, making it easy to scan and action.

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 lack of annotations and output schema, the description covers the essential purpose and the key limitation (no line items), which is sufficient for basic decision-making. It could mention return values or update semantics, but the alternative note substantially completes the contextual picture.

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 provides descriptions for all parameters (100% coverage), so the baseline sits at 3. The description merely echoes the schema's attribute names without adding additional semantic nuance like merge behavior or field formatting.

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 explicitly states it updates order attributes and lists concrete examples (email, shipping address, tags, notes). It clearly distinguishes itself from line item editing tools in the sibling list, leaving no ambiguity about its scope.

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?

It explicitly instructs users to use 'order editing' for line item changes, providing a clear alternative and setting a precise boundary. This is exactly the kind of when-to-use vs. when-not-to-use guidance that helps an agent select correctly.

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