whmcs_pending_orderSet a WHMCS order status to pending using the order ID. Resolves order management workflows by updating order status directly via API.
Set an order status to pending
| 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?
No annotations are present, and the description does not disclose any behavioral details beyond the basic action. Missing information includes whether the operation is reversible, triggers workflows, requires specific permissions, or has any side effects.
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, clear sentence with no unnecessary words. It is appropriately concise for a simple tool.
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 context of many sibling status-related tools, the description is too minimal. It does not explain what 'pending' means, how it differs from other statuses, or what the outcome is. For a single-parameter tool, more context would be helpful for correct tool selection.
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 100% coverage, with the parameter 'orderid' having a description of 'Order ID'. The description adds no additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate.
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 ('Set an order status to pending') with a specific verb and resource (order status). It distinguishes itself from sibling tools like whmcs_accept_order, whmcs_cancel_order, and whmcs_fraud_order, which set different statuses.
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?
No guidance is provided on when to use this tool versus alternatives (e.g., accept_order, cancel_order). There is no mention of prerequisites, order states, or when setting to pending is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.