move_fulfillment_order

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

No annotations are available, so the description carries the full burden. It only states the action with no details on side effects, prerequisites, order state requirements, or reversibility, leaving the agent unaware of important behavioral constraints.

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 directly states the action without any unnecessary words or filler. It is appropriately concise for the tool's simplicity.

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?

While the two-parameter schema is fully documented and the action is simple, the description omits contextual details such as when the move is allowed, constraints on the fulfillment order or destination location, and what the response contains. It is minimally viable but not complete.

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 covers both parameters (id and newLocationId) with 100% description coverage, so the description adds little beyond what the schema already provides. It does reinforce the purpose ('different location for fulfillment') but no additional syntax or format details.

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 uses a specific verb 'move' with a clear resource 'fulfillment order' and destination 'different location for fulfillment'. This clearly distinguishes it from sibling fulfillment tools like cancel_fulfillment_order, hold_fulfillment_order, or reschedule_fulfillment_order.

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 explicit usage guidance is provided, but the action is specific enough that the intended use case (moving a fulfillment order to a new location) is implied. It does not mention alternatives or exclusions, so it offers limited differentiation from other fulfillment operations.

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