Cancels an eligible eSIM order before activation/provisioning. Requires a valid session token.
| Name | Required | Description | Default |
|---|---|---|---|
| token | No | The secure session token returned by verify_agent_otp. | |
| orderId | Yes | The ID of the order to cancel. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses the cancellation action and a prerequisite, but does not describe side effects (e.g., irreversibility), authorization details beyond token, or error handling.
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 concise sentences, no waste. The essential information is front-loaded and 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?
Given no output schema and no annotations, the description is minimal. It covers the basic purpose and a prerequisite but lacks details on success/failure behavior, eligibility criteria, or post-cancellation effects.
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 coverage is 100%, so the baseline is 3. The description reinforces the token requirement and contextualizes orderId as belonging to an eSIM order, but does not add significant new meaning beyond the schema.
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 specifies the action ('cancels'), the resource ('eSIM order'), and a condition ('before activation/provisioning'). It clearly identifies what the tool does, and there is no sibling tool with similar purpose.
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 states a prerequisite ('Requires a valid session token'), but does not provide guidance on when to use the tool versus alternatives, nor conditions where cancellation is ineligible.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
