Post bulk collections

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

Annotations already state readOnly=false, destructiveHint=false, and openWorld=true, so the safety profile is partly covered. The description adds that this is a bulk assignment, but it does not explain whether assignments are additive or replacing, what permissions are required, or what happens to existing collection membership.

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 filler. However, its brevity becomes under-specification given the opaque three-parameter schema.

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 mutation with three completely undocumented parameters and no output schema, the description is far too thin. It gives the high-level concept but leaves an agent unable to construct a correct request.

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 all three parameters ('form', 'params', 'json_body') have no types or descriptions. The description does not explain these parameters or map the cipher/collection payload to the schema at all.

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 clear verb and resource: 'Bulk-assign a set of ciphers to collections.' It is more specific than the title 'Post bulk collections,' but it does not distinguish this tool from close siblings such as vaultwarden_post_bulk_access_collections.

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?

It implies a bulk-assignment scenario but gives no guidance on when to use this instead of related collection/cipher assignment tools. No prerequisites, exclusions, or alternative tools are named.

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