Restore cipher put admin

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

Annotations already declare this is a non-read-only, non-destructive, open-world operation, and 'restore from trash' is consistent with that mutation profile. The description adds that it affects exactly one cipher and follows an admin route, but it does not describe admin authorization requirements or what the restore returns.

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 single sentence is front-loaded and has no wasted words. It is efficient, though its brevity contributes to the missing detail elsewhere rather than being a standalone strength.

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 four-parameter mutation tool with no schema descriptions and no output schema, the definition is too thin. It omits admin permission requirements, parameter usage, and any indication of the response or side effects, leaving an agent under-informed for correct invocation.

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%, so the description must carry parameter meaning. 'One cipher' weakly maps to the required cipher_id, but it says nothing about the form, params, or json_body arguments, leaving three parameters completely unexplained.

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 (restore one cipher) plus the source (trash) and route (admin path). It distinguishes itself from the non-admin restore_cipher_put sibling through the 'admin path' qualifier, though it does not name that sibling explicitly.

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?

Beyond the phrase 'via admin path', there is no guidance on when to choose this over vaultwarden_restore_cipher_put, vaultwarden_restore_cipher_selected, or vaultwarden_restore_cipher_selected_admin. The admin-vs-user distinction is implied but never stated as a selection rule.

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