Delete an FTP account from cPanel by username and domain, with an option to also remove the account's home directory.
Delete an FTP account
| Name | Required | Description | Default |
|---|---|---|---|
| user | Yes | FTP username to delete | |
| domain | Yes | Associated domain | |
| destroy | No | Also delete the FTP user's home directory |
Changes observed during successful MCP inspections.
v2.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It only states 'Delete an FTP account' without mentioning irreversibility, impact on home directory, or the optional 'destroy' parameter. This is a significant transparency gap for a destructive operation.
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 extremely short and front-loaded, but it is under-specified. It does not earn a high score for conciseness because it omits critical context, making it more sparse than concise.
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?
The tool has three parameters and no output schema, so the description must provide sufficient context. It fails to mention the optional 'destroy' behavior, whether deletion is permanent, or any side effects on data. The description is incomplete for safe and informed use.
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%, and each parameter has a description. The tool description adds no extra parameter meaning, so it earns the baseline score of 3. No additional semantics are needed 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 'Delete an FTP account' uses a specific verb and resource, clearly distinguishing it from sibling tools like create_ftp_account, change_ftp_password, and list_ftp_accounts. It is unambiguous and precise.
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 implies the tool is for deleting FTP accounts but provides no explicit guidance on when to use it vs alternatives, nor any exclusions or prerequisites. It relies on the user's understanding of the operation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.