Move cipher selected

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 description adds little. It does contribute the "bulk" scope and the fact that a removal mode exists, but it omits whether folder membership is replaced or appended, what permissions are required, and what happens on partial failure across the bulk set.

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?

One short sentence with the action front-loaded and no filler. Its brevity is appropriate, though the parenthetical is slightly cryptic about how removal is expressed.

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 bulk mutation tool with three completely undocumented free-form parameters, no output schema, and a near-duplicate sibling is not adequately specified by a single nine-word sentence. The description should at minimum say which fields carry the selection and the destination folder.

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% and all three parameters (form, params, json_body) are untyped and undescribed. With that gap the description must compensate, but it never says where the cipher IDs or target folder ID go, nor how the remove variant is signaled.

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 gives a specific verb and resource ("bulk move ciphers into a folder") plus the remove-from-folder variant, so the general action is clear. However it does not distinguish this tool from the near-identical sibling vaultwarden_move_cipher_selected_put, which appears in the sibling list, leaving the agent guessing which of the two to call.

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 guidance on when to use this versus the _put sibling, versus archive/restore, or versus a single-cipher update. The parenthetical "(or remove from folder)" hints at the removal case but never says how that case is expressed in the request.

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