Vaultwarden Maintenance

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

With no annotations, the description carries the full burden, and it does disclose real behavior: results return item ids and counts only, applying/rotating requires confirm: true, and a loose deduplication plan is never auto-applied. It omits permission/auth requirements and failure behavior, keeping it short of a 5.

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 purpose is front-loaded in the first sentence, followed by tightly packed behavioral constraints. The trailing 'CONCEPT:VW-ECO.mcp.maintenance-operations' tag is boilerplate that does not earn its place, costing a point.

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?

An output schema exists, so return values need not be explained, and the safety gating is covered. But for a multi-action tool whose real parameters are hidden in an opaque params_json object, the description gives no per-action parameter guidance, leaving a meaningful gap.

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 100%, so the baseline is 3, but the description adds value by revealing a 'confirm: true' flag that must be supplied inside params_json and is not documented in the schema. It still does not describe what params_json should contain for each action (e.g., which item id rotate_password needs).

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 opening sentence names specific verbs and resources: plan/apply deduplication and rotate/generate passwords. It is clearly distinct from the sibling tool set (accounts, ciphers, folders, etc.), which are all CRUD/resource tools, though the description never explicitly contrasts itself with them.

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?

Usage is implied through the enumerated actions and the gating rules (apply/rotate need confirm: true), which tells the agent when a write is permitted. However, there is no explicit when-to-use-this-vs-alternatives statement or guidance on which action to pick in a given situation.

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