reschedule_fulfillment_order

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not mention prerequisites (e.g., whether the order must be in a specific status), side effects, or the response format. As a mutation tool, this is insufficient.

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 sentence that directly states the tool's purpose. It is concise, front-loaded with the verb, and contains no superfluous information.

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 mutation tool with moderate complexity, the description is too sparse. It lacks critical context about fulfillment order states (e.g., only 'scheduled' orders can be rescheduled), potential side effects, or expected return values. Given the absence of an output schema and annotations, this is a notable gap.

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 with descriptions (id and fulfillAt), achieving 100% coverage. The description adds no extra semantic value beyond the schema, but that is acceptable given the 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 specific action ('Reschedule'), the resource ('a scheduled fulfillment order'), and the target ('to a new date and time'). It distinguishes the tool from siblings such as cancel_fulfillment_order and hold_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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention preconditions or exclusions. It simply states what the tool does, leaving the agent without enough context to decide if this is the right tool for a given situation.

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