Post collections2 update

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 write/safety profile is partially covered by structured data. The description adds nothing beyond that: it does not say what is mutated, whether the update is partial or full replacement, or what permissions are needed for a collection write.

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 definition is only five words, so it is trivially concise, but that is under-specification rather than economy. The one useful token (v2/POST alias) is present, but nothing is front-loaded toward what the tool actually does.

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 endpoint with four undocumented parameters, no output schema, and at least three near-duplicate siblings requires far more than this. An agent cannot determine the request body or distinguish it reliably from the PUT alias, so the definition is not sufficient to call the tool correctly.

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?

Four parameters with 0% schema description coverage and no descriptions at all — form, params, json_body and even the required cipher_id have no type or meaning documented. The description contributes no parameter information whatsoever, leaving an agent to guess the shape of the payload it must POST.

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?

"Set collections (v2, POST alias)" names a resource and gestures at an update action, and the "v2, POST alias" tag does distinguish it from the PUT and non-v2 siblings in the list. However, "Set collections" is close to a restatement of the tool name, and it never says what aspect of the collections is being set (membership? permissions? the collection record itself?).

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?

The parenthetical "(v2, POST alias)" implies this is the POST-flavored duplicate of the v2 collections update, which is a weak implicit signal. There is no statement of when to choose it over vaultwarden_put_collections2_update or vaultwarden_post_collections_update, and no prerequisites or auth context.

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