Put folder

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds nothing beyond the word "rename" — it does not say whether the folder must exist, whether ciphers inside are affected, what permissions are needed, or what is returned. For a mutation tool the added context is minimal.

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?

Three words are concise but the problem here is under-specification, not tightness. There is no structure to speak of and nothing front-loaded beyond the barest action label.

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?

A mutation tool with four parameters at 0% schema coverage, no output schema, and only a three-word description leaves an agent unable to determine how to supply the new name, what the wrapper parameters mean, or what success looks like. Given the complexity, this is clearly inadequate.

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 four parameters exist, including opaque generic wrappers (form, params, json_body) plus an undocumented folder_id. The description mentions no parameter at all, not even that folder_id identifies the folder to rename, so it does nothing to compensate for the schema gap.

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?

"Rename a folder" names a specific verb and resource, so the basic action is clear. However, the tool name and title say "Put folder", which implies a broader update/replace of folder state, and the description neither reconciles that with "rename" nor distinguishes this from sibling writers like vaultwarden_post_folder, vaultwarden_put_folders, or vaultwarden_delete_folder.

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 indication of when to use this versus alternatives such as creating a folder, or whether it requires an existing folder created elsewhere. No prerequisites, no exclusions, no mention of the sibling tools that operate on folders.

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