Unarchive cipher selected

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description is not contradicted, but it adds nothing beyond the title — no info on how ciphers are selected, whether the operation is idempotent, or what permission scope is needed. For a mutation tool, the extra context is essentially absent.

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, front-loaded and waste-free, but the brevity reflects under-specification rather than economy — the same length could have carried selection semantics.

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?

With fully opaque parameters, no output schema, and no annotation detail about scope or effects, the definition is far too thin for a bulk mutation over ambiguous form/params/json_body inputs. An agent cannot reliably construct a valid call from it.

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?

Three parameters (form, params, json_body) with 0% schema description coverage and no constraints or types, and the description says nothing about them. The agent has no way to know where the cipher IDs go or what shape the payload takes.

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?

"Bulk unarchive ciphers" names a specific verb and resource, so the action itself is unambiguous. However, it does not distinguish this from the sibling vaultwarden_unarchive_cipher_put (single-cipher variant) or explain what "selected" means, leaving the bulk-versus-single routing to the name alone.

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 alternatives such as vaultwarden_unarchive_cipher_put or vaultwarden_archive_cipher_selected. The agent must infer the choice purely from the tool name.

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