whmcs_delete_ticketDelete a support ticket from WHMCS by its ticket ID. Use caution, as this action permanently removes the ticket.
Delete a support ticket (use with caution)
| Name | Required | Description | Default |
|---|---|---|---|
| ticketid | Yes | Ticket ID to delete |
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 responsibility for behavioral disclosure. It indicates deletion and cautions, but fails to explain permanence, impact on related data (e.g., ticket notes), or required permissions. A destructive action requires more detail.
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 short—one sentence with no unnecessary words. However, it could be slightly expanded to include key behavioral details 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 simplicity of the tool (one parameter, no output schema), the description is somewhat complete. However, for a destructive action, more context about consequences and permissions is needed to fully inform an agent.
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 for the single parameter, and the description adds no new information beyond what is already in the schema description. The baseline 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 action ('delete') and the resource ('support ticket'). However, it does not distinguish this tool from sibling ticket tools like whmcs_open_ticket or whmcs_update_ticket, which could lead to confusion.
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. The phrase 'use with caution' is a generic warning, not a usage guideline. There is no mention of prerequisites, side effects, or when not to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.