Delete an FTP account from a CentOS Web Panel hosting account. Provide the account username and FTP username to remove access.
Delete an FTP account for a user
| Name | Required | Description | Default |
|---|---|---|---|
| user | Yes | Username of the account | |
| username | Yes | FTP username to delete |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden but only says 'Delete'. It does not disclose whether the deletion is permanent, whether associated files/home directory are removed, or what permissions are required to invoke it.
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?
A single front-loaded sentence with zero filler; the verb and object are stated immediately.
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?
For a destructive mutation with no annotations and no output schema, the description should at least flag irreversibility or side effects. It leaves the agent unable to judge risk or consequences of the call.
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 description coverage is 100%, with both 'user' and 'username' documented in the schema. The description adds no syntax, format, or distinction beyond that, so the schema does all the work — baseline 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?
States a specific verb and resource ('Delete an FTP account') and scopes it to a user, which clearly separates it from cwp_ftp_create, cwp_ftp_list, and cwp_ftp_update_permissions. It does not explicitly name siblings, but the operation is unambiguous.
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 on when to use this versus alternatives, no prerequisites (e.g., does the account need to be suspended first?), and no confirmation or irreversibility notes for a destructive operation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.