Delete attachment admin

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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the destructive nature is covered. The description adds only 'admin path' as extra context; it does not say whether deletion is permanent, what permissions are required, or what happens to the parent cipher. With annotations carrying the main safety signal, this is adequate but thin.

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 short phrase with no wasted text, and the action is front-loaded. However, its brevity leaves important context unstated rather than making every sentence earn its place.

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?

This is a destructive administrative mutation with five parameters, no schema descriptions, and no output schema. The description provides only the minimal action and admin-path note, which is not enough to help an agent call it correctly or understand its scope.

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 the description does not explain the five parameters. It implies attachment_id via 'attachment' but never explains cipher_id or the form/params/json_body fields, so an agent must infer required parameter meanings entirely from names.

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 states a specific verb and resource: deleting an attachment, with an 'admin path' qualifier. It clearly distinguishes the operation from generic attachment retrieval, though it does not explain how it differs from the many other delete-attachment variants such as vaultwarden_delete_attachment or vaultwarden_delete_attachment_post.

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 phrase 'admin path' hints that this is for an administrative endpoint, but there is no explicit guidance on when to use this versus the non-admin vaultwarden_delete_attachment or the POST variants. No prerequisites, exclusions, or alternative-selection criteria are provided.

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