whmcs_delete_orderDelete a WHMCS order by its order ID to remove unwanted or erroneous orders from the system. Use this action to permanently remove an order record when deletion is required.
Delete an order (use with caution)
| Name | Required | Description | Default |
|---|---|---|---|
| orderid | Yes | Order ID |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears full burden. 'Use with caution' hints at destructiveness but lacks detail on reversibility, cascading effects (e.g., on invoices or products), or required permissions.
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 very concise (6 words plus a parenthetical), with no wasted words. Although brief, it conveys the core action. However, it could be slightly more informative without sacrificing conciseness.
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 the simple nature (single parameter, no output schema), the description covers the basics but lacks important context about consequences, making it only minimally 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 has one parameter (orderid) with full coverage and a description ('Order ID'). The tool description adds no additional meaning, so baseline score of 3 applies.
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 verb 'delete' and resource 'order', matching the name and title. However, it does not explicitly differentiate from sibling tools like whmcs_cancel_order or whmcs_fraud_order, which have similar purposes.
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 only offers a warning ('use with caution') but provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or side effects.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.