update_order_status

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

With no annotations, the description must carry the burden of behavioral disclosure. It only states 'Update order status' without mentioning side effects, permissions, transition restrictions, or whether the change is reversible. This is insufficient for a mutating operation.

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, front-loaded sentence that is efficient and easy to parse. It includes concrete examples, but lacks the structural richness of a top-tier description. Still, it earns a 4 for being appropriately minimal without waste.

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?

This is a write tool with no annotations, no output schema, and only a minimal description. The agent is left unsure about response format, error handling, or operational consequences (e.g., does updating to 'cancelled' send notifications?). The description is incomplete for making fully informed invocations.

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 provides full descriptions for all three parameters, including an enum for status. The description adds no additional meaning beyond restating that the status changes, so it meets the baseline of 3 for high schema coverage.

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 action ('Update order status') and the specific resource, making it distinct from siblings like get_order_details or update_product_stock. It also lists example status values, which reinforces the purpose. However, it does not explicitly differentiate from other update tools or mention scope (e.g., merchant-only), so it falls short of a 5.

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 no guidance on when to use this tool versus alternatives. It does not mention who should use it (e.g., merchant) or exclusions (e.g., customer tracking uses track_customer_order). No context for decision-making is given.

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