cancel_order_items

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

With no annotations present, the description takes on the full burden and adds real behavioral context: it calls out the required role, the absence of a cancellation-reason field, and the fact that the audit log only records who/when, not the business reason. It does not explicitly disclose whether cancellation is irreversible or how it affects order state, but it covers the most important operational caveats.

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?

Two sentences with no filler: the action is front-loaded, then the role requirement, then the meaningful caveat about the audit log and business reason. Every clause earns its place and the structure is easy to parse.

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 single-parameter tool with no output schema, the description is reasonably complete: it states the operation, the role requirement, and an important reporting caveat. It could additionally note whether cancellation is reversible or what response/error behavior to expect, but those are less critical given the tool's simplicity.

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 0%, so the description must compensate. The phrase 'one or more order items' implies the order_item_ids array must contain at least one valid item ID, and the reference to no cancellation-reason field clarifies an absent parameter. Still, the description does not explicitly explain the format or source of order_item_ids, leaving some semantics to be inferred from the property name.

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 states the exact operation ('Cancel one or more order items') with a specific verb and resource. This clearly distinguishes it from sibling tools like get_order_items, pack_orders, and mark_ready_to_ship, which are read or status-transition operations rather than cancellations.

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 gives a clear prerequisite (VC - Order Manager role) and a context around the cancellation reason, which is helpful for deciding applicability. However, it does not explicitly mention when not to use this tool or point to an alternative (e.g., retrieving items first via get_order_items), so some guidance is left to inference.

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