Post delete account

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds important behavioral context: deletion requires password/OTP confirmation in the body. It does not explicitly emphasize irreversibility or describe the account data being removed, but it does disclose a key auth requirement.

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 no wasted words, and the core action is front-loaded. Its terseness contributes to the parameter and usage gaps, but as a conciseness/structure measure it is efficient.

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 self-account deletion operation with three undocumented parameters and no output schema, the description is too sparse. It mentions confirmation in the body but does not explain the body schema or the roles of the other parameters, leaving the agent without enough detail to invoke it confidently.

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% for three parameters (form, params, json_body), and the description only vaguely indicates that password/OTP confirmation goes in the body. It does not explain how to populate form or params, nor the structure of the confirmation payload.

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 and resource: "Delete own account." The word "own" scopes it to self-service deletion and distinguishes it from administrative delete siblings, though no sibling is named explicitly.

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 implies when the tool applies by saying "Delete own account," but it provides no explicit guidance on when to use it versus alternatives such as vaultwarden_delete_account or admin deletion tools. The parenthetical only describes confirmation, not usage conditions.

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