Removes a specified public or private SSH key by name from a cPanel account, helping clean up unused credentials or revoke access.
Delete an SSH key
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Key name to delete | |
| type | Yes | Whether to delete public or private key |
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 behavior. It only states 'Delete an SSH key' without mentioning that deletion is permanent, whether it affects authorized keys or connections, or if any confirmation or rollback exists. This is inadequate 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?
One short sentence with no filler. It is appropriately concise for a simple operation.
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 tool with sibling operations like deauthorize_ssh_key, the description is under-specified. It lacks information about the implications of deleting public vs private keys, whether the key must be in use, and the irreversible nature of the operation. The schema and sibling tools suggest more complexity than the description addresses.
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 fully describes both parameters with descriptions ('Key name to delete', 'Whether to delete public or private key'), so the description adds no extra semantic value. 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?
The description uses the specific verb 'Delete' and names the resource 'SSH key', clearly distinguishing it from sibling tools like list_ssh_keys, import_ssh_key, authorize_ssh_key, and deauthorize_ssh_key. It is concise and 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?
The description provides no context for when to delete an SSH key versus deauthorizing it or removing it from authorized keys. Sibling tools include deauthorize_ssh_key, and no distinction is made.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.