Apply Deduplication

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

Beyond the annotations, it discloses the confirm gate, a safety guard against auto-applying a loose plan, and the shape of results ('item ids and counts only'). It does not say what happens if confirm is omitted (error vs no-op), which is the one behavior an agent most needs before calling.

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 action and its constraints are front-loaded, but the middle sentence about plan/apply, rotation, and password generation describes sibling tools rather than this one, which dilutes focus. The trailing CONCEPT tag adds no decision value.

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 an output schema present and annotations covering mutability hints, the description supplies the key extras: the confirm requirement, the result shape, and the no-auto-apply guard. Only the failure mode for a missing confirm and the link to the plan tool are 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 100% but the single params_json field is documented only generically, so the description's mention of 'confirm: true' is the sole hint that a specific key is required inside the JSON blob. That is useful but leaves the rest of the expected payload opaque.

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 first line states a specific verb+resource (apply deduplication on the vault) and scopes it to the maintenance family. However, it then lumps in 'rotate or generate passwords', which are separate sibling tools (vaultwarden_maintenance_rotate_password, vaultwarden_maintenance_generate_password), blurring the boundary of what this tool alone does.

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 establishes a real precondition ('requires confirm: true') and a safety rule ('a loose deduplication plan is never applied automatically'), which tells the agent when invocation is legitimate. But it never names vaultwarden_maintenance_plan_deduplication as the required precursor, leaving the plan-then-apply workflow implicit.

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