vaultwarden_delete_accountPermanently deletes the authenticated user's own Vaultwarden account via REST DELETE, enabling account removal when access is no longer needed.
Delete own account (REST DELETE alias)
| Name | Required | Description | Default |
|---|---|---|---|
| form | No | ||
| params | No | ||
| json_body | No |
Changes observed during successful MCP inspections.
v0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the "REST DELETE alias" hint, which is mildly useful for method semantics but says nothing about irreversibility, what data is removed alongside the account, or whether the operation is reversible. Given how consequential this call is, that is a meaningful gap.
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 single sentence is front-loaded and wastes no words, but it is terse to the point of under-specification for a destructive tool. Brevity here comes from omission rather than efficiency.
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?
With three undocumented generic parameters, no output schema, and a destructive annotation, the description leaves an agent without the information needed to invoke this safely or correctly. At minimum it should explain the payload shape and confirm the deletion is permanent.
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 the three parameters (form, params, json_body) are declared with no titles beyond their names and a null default. The description supplies no information about what any of them should contain, so an agent has no way to populate them correctly.
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 own account") and the word "own" scopes it away from admin variants like vaultwarden_delete_user. It does not distinguish itself from the sibling vaultwarden_post_delete_account, which appears to be the same operation over a different HTTP method.
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 choose this over vaultwarden_post_delete_account, and no prerequisites stated (password/2FA confirmation, purge of vault data). A destructive self-service deletion call with an equivalent sibling deserves explicit routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.