Delete folder post

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

The annotations already declare this as destructive, non-read-only, and open-world. The description restates "delete" and notes the POST alias but adds no context about what exactly is destroyed, whether contents are affected, permission requirements, or confirmation behavior.

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 front-loaded sentence with no wasted text. Its brevity is efficient, though it contributes to the completeness gaps captured elsewhere.

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 folder-deletion operation with four parameters and no output schema, the description is too thin. It identifies the action but does not explain the alias choice, parameter usage, or behavioral consequences beyond what annotations already state.

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?

With 0% schema description coverage and four parameters, the description provides almost no parameter guidance. "Folder" loosely implies folder_id, but the roles of form, params, and json_body are completely undocumented.

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 clear verb and resource: "Delete a folder," and adds "(POST alias)" to signal an HTTP-method variant. It is distinguishable from the primary delete-folder sibling, though it does not fully explain when to prefer this alias over the standard one.

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?

There is no explicit guidance on when to use this tool versus vaultwarden_delete_folder or other folder operations. The only usage signal is the parenthetical "POST alias," leaving the agent to infer selection criteria.

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