Delete folder

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so safety is covered structurally. The description contributes nothing beyond that—no statement that the folder and its contents are permanently removed, no permission or cascading-effect notes.

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 short and front-loaded, but it carries no information beyond the tool name, so its brevity is under-specification rather than conciseness.

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, open-world mutation with four undocumented parameters, no output schema, and a near-identical sibling, this description supplies nothing an agent needs to invoke it correctly or safely.

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% across 4 parameters, including opaque ones like 'form', 'params', and 'json_body', and the description explains none of them. Only 'folder_id' is required, but nothing tells the agent what the other fields are for or when to supply them.

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 'Delete a folder' merely restates the tool name and title with no additional specificity. It does not distinguish this tool from the near-duplicate sibling vaultwarden_delete_folder_post, nor from vaultwarden_folders_create_folder or vaultwarden_put_folder, so an agent cannot tell which delete variant to pick.

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 when-to-use guidance, no prerequisites, and no mention of the alternative vaultwarden_delete_folder_post. Given the crowded sibling set of delete endpoints, silence here leaves the agent to guess.

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