Permanently remove a saved SSH key from your account to prevent it from being used in future VPS deployments. Requires explicit confirmation; existing VPS instances remain unaffected.
Permanently delete a saved SSH key from this account. Irreversible — requires confirm=true. Does not affect VPS instances it's already been installed onto, only future deploys.
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | No | ||
| ssh_key_id | Yes |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true, but the description adds critical behavioral details: irreversibility, requirement for confirm=true, and the scope of impact (doesn't affect existing VPS installs). This goes beyond the annotation and is essential for safe invocation.
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?
Three concise sentences. The primary action is front-loaded, followed by essential caveats. No redundant wording or valuable space wasted.
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 tool with 2 parameters and no output schema, the description covers the purpose, irreversible nature, confirm requirement, and behavior regarding existing VPS instances. Nothing critical is missing for an agent to invoke it correctly.
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 0%, so the description must compensate. It explicitly explains the confirm parameter ('requires confirm=true'), which is non-obvious. The ssh_key_id parameter is self-explanatory from its name. This adequately covers the parameters given the low schema coverage.
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 states a specific verb ('delete'), a specific resource ('saved SSH key'), and the scope ('from this account'). It clearly distinguishes from sibling tools like create_ssh_key and list_ssh_keys by naming the action and object.
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 conveys the usage context by stating it is for permanent deletion and notes that it does not affect VPS instances already installed, only future deploys. However, it does not explicitly name alternative tools or provide 'when not to use' guidance, though siblings are self-evident.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.