Delete cipher selected put admin

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description does add real value by specifying 'soft-delete', meaning items move to trash rather than being permanently destroyed, and 'admin path' signals elevated-privilege scope — both facts annotations cannot express.

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?

Five words with no wasted phrasing, but the brevity reflects missing content rather than disciplined editing. What remains is front-loaded yet too thin to guide selection or invocation.

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 destructive, admin-scoped bulk mutation with no output schema and three undocumented parameters, the definition leaves critical gaps: selection payload shape, required privileges, confirmation semantics, and per-item failure behavior are all unstated.

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?

All three parameters (form, params, json_body) have 0% schema description coverage, are untyped with default null, and carry no enums — the description compensates for none of this. It never indicates where the list of selected cipher IDs goes, so an agent cannot construct a correct call from either source.

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?

'Bulk soft-delete via admin path' names a specific action (bulk soft-delete) and a scope (admin path), but never states the resource — ciphers — relying on the tool name to supply it. It also doesn't differentiate from the many near-identical siblings (delete_cipher_selected, delete_cipher_selected_put, delete_cipher_selected_post_admin) beyond the vague words 'admin path'.

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?

No statement of when to use this over the non-admin or POST variants, no prerequisites, and no mention that admin/org-level privileges are implied. The only hint toward selection is the word 'bulk', which tells the agent it acts on multiple ciphers but not how the selection is passed.

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