Shipping_cancelShipment

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says the action cancels a shipment and runs remotely in Kuudo. It omits side effects, reversibility, refund implications, permissions, and any post-cancellation behavior.

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 short and efficient, with no wasted words. The 'Catalog entry' opener is awkward and the main action is placed last, but overall the structure is appropriately minimal.

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 no annotations, no output schema, and an effectively open input schema, this description is too thin. It lacks invocation details, expected identifiers, behavioral effects, and any differentiation from similarly named cancellation tools.

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?

There are zero declared parameters, so the schema provides no parameter names. However, because additionalProperties is true, the agent still lacks guidance on how to identify the shipment to cancel, and the description does not fill that gap.

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 operation: it 'cancels a purchased shipment,' with a specific verb and resource. However, it does not differentiate this tool from related cancellation tools in the sibling list such as ShippingLegacy_cancelShipment or MerchantFulfillment_cancelShipment.

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 no guidance on when to use this tool versus alternatives. The note that it 'runs in your Kuudo deployment, not here' hints at the execution context but does not help an agent decide between this and the many other cancel-related operations available.

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