vaultwarden_delete_cipher_post_adminPermanently deletes a Vaultwarden cipher through the admin API by cipher ID, enabling administrators to remove vault items when standard deletion is unavailable or insufficient.
Permanently delete a cipher via admin path
| Name | Required | Description | Default |
|---|---|---|---|
| form | No | ||
| params | No | ||
| cipher_id | Yes | ||
| json_body | No |
Changes observed during successful MCP inspections.
v0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds useful context by saying the deletion is permanent and admin-path scoped, but it does not explain required admin permissions, auth flow, or side effects beyond deletion.
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 short sentence with the key action and scope front-loaded. Every word contributes and there is no filler.
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 admin deletion with four parameters, 0% schema description coverage, and no output schema, the definition is too sparse. The annotations cover destructiveness, but the description leaves admin requirements, parameter usage, and method-specific behavior unexplained.
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%, and four parameters exist. The description implies that a cipher is targeted, which helps infer cipher_id, but it gives no meaning for the other parameters such as form, params, or json_body.
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 gives a specific verb, resource, and scope: permanently delete a cipher via the admin path. It distinguishes the admin variant from non-admin siblings, but does not clarify how it differs from other admin deletion variants such as POST vs PUT or selected-cipher deletions.
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 states what the tool does but gives no explicit guidance on when to use it instead of sibling deletion tools. 'via admin path' implies an administrative context, but there are no exclusions or named alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.