fulfillment_cancel

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

No annotations are provided, so the description must bear the full burden of behavioral disclosure. It mentions cancellation is conditional but does not describe what happens if the order is not cancellable (error? no-op?), nor does it mention side effects, authentication requirements, or idempotency. For a mutation tool, this is lacking.

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 concise with three short sentences. It is front-loaded with the action and resource. However, it could be more structured (e.g., using a clear when statement).

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 simple tool with one parameter and no output schema, the description covers the basic purpose and usage condition. However, it is incomplete in explaining the result of the action, error handling, or prerequisites beyond shipment status. Given the large sibling set, more nuance would help.

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 description adds minimal value beyond the schema for the single parameter order_id. It says 'Order ID to cancel,' which is nearly tautological. With 0% schema coverage, the description should provide more context (e.g., format, source, or validation).

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 (cancel) and resource (fulfillment order), and explicitly adds the condition 'if still cancellable' and 'Only orders that have not yet shipped can be cancelled.' This distinguishes it from sibling tools like cancel_job and cancel_print which operate on different resources.

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?

Provides a clear condition for when the tool is applicable: orders that have not shipped. This gives the agent a when-not rule. However, it does not explicitly name alternative tools for orders that have already shipped, which would boost the score.

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