Removes an existing subdomain from cPanel using its full domain name, such as blog.example.com, so you can clean up unused hostnames.
Delete a subdomain
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | Yes | Full subdomain (e.g., 'blog.example.com') |
Changes observed during successful MCP inspections.
v2.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of disclosing behavioral traits. It merely restates the tool name without mentioning side effects, reversibility, or dependencies. For a destructive operation, this is critically insufficient.
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, concise sentence with no unnecessary words. It is efficiently structured, though it sacrifices informativeness for brevity.
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?
Despite the tool's simplicity, the description lacks crucial context for a deletion operation, such as whether it is idempotent, what happens to associated records, or error behavior. The low complexity is not leveraged to add meaningful depth.
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 schema provides 100% coverage for the sole parameter 'subdomain' with a clear example. The tool description adds no parameter information, but the baseline of 3 is appropriate given the schema's completeness.
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 'Delete a subdomain' uses a specific verb and resource, unambiguously stating the tool's action. It clearly distinguishes from sibling tools like 'create_subdomain' and 'delete_addon_domain'.
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, nor are there any prerequisites or exclusions. The description gives no context about when deletion is appropriate or what other tools might be involved.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.