Post ciphers import

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

Annotations already cover the safety profile (non-destructive write, open-world), so the description needed to add import-specific behavior. It does not say whether the import merges with or overwrites existing vault contents, how duplicates are handled, whether it is transactional/atomic, or whether authentication/org membership is required — all material for an import operation.

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?

A single front-loaded sentence with no filler, and the distinguishing 'one call' detail is placed where it is seen first. It is arguably too short for the operation rather than padded.

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 bulk, payload-driven import with no output schema and zero-documented parameters, the description leaves an agent unable to construct a valid call or predict side effects. The safety annotations help, but the input contract and merge semantics are entirely absent.

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% for three undocumented params (form, params, json_body). The description only obliquely implies that ciphers and folders go into the payload; it says nothing about the expected structure, required fields, or why there are three separate input channels.

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?

States a specific verb ('Bulk import') and the resources involved ('ciphers + folders'), plus the key distinction of doing both in one call. It is not fully differentiated from siblings such as vaultwarden_post_org_import, vaultwarden_ldap_import, or vaultwarden_post_ciphers, but the core purpose is unambiguous.

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?

'in one call' hints at batch efficiency but gives no conditions for choosing this over vaultwarden_post_cipher, vaultwarden_post_ciphers, or vaultwarden_post_org_import. No prerequisites, no exclusions, no mention of when a bulk import is appropriate versus repeated creates.

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