Delete user

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and openWorldHint=true, and 'Permanently' reinforces irreversibility, which is real added value. But the description says nothing about what data is destroyed alongside the account (ciphers, attachments, org memberships), whether admin privilege is required, or whether the action is logged/auditable.

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 no wasted words; the destructive qualifier is placed first. It is efficient but so terse that the brevity comes at the cost of missing guidance rather than being a virtue.

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, irreversible, admin-scoped operation with four parameters, zero schema description coverage, and no output schema, one sentence is not enough. An agent cannot tell what will be cascaded, what identifier form user_id expects, or how this differs from the several other user-deletion tools.

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 coverage is 0% — user_id is an untyped property and the three optional wrapper fields (form, params, json_body) are undocumented. The description only implies that a user account must be identified, adding no format, ID-type, or sourcing information to compensate for the empty schema.

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 ('Permanently delete an instance user account'), and the word 'instance' usefully scopes it to a server-level account rather than an org membership. However, it does not distinguish itself from close siblings such as vaultwarden_delete_account, vaultwarden_delete_sso_user, vaultwarden_disable_user, or vaultwarden_bulk_delete_member, so an agent must infer the difference.

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 disable_user (reversible) or delete_sso_user/delete_account, and no prerequisites stated. The only usage signal is the adverb 'Permanently', which implies irreversibility but not a selection rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.