Delete cipher selected

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is clear. The description adds 'permanently' and 'bulk,' reinforcing that this is an irreversible multi-item mutation, but it does not disclose authorization requirements, confirmation behavior, or whether deletion is soft/hard beyond the adjective 'permanently.'

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 wastes no words. Its terseness is efficient, though it leaves important detail unstated rather than being bloated.

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 bulk-delete operation with three undocumented parameters and no output schema, the description is too thin. It omits prerequisites, id-list format, expected behavior on partial failure, and distinctions from the many sibling delete variants.

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 all three parameters (form, params, json_body) are opaque. The description says deletion happens 'by id list,' which gives minimal semantic context, but it does not indicate which parameter carries the id list or what the other two parameters do.

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 (delete), resource (ciphers), and scope (bulk, permanently, by id list). It is clear enough to distinguish from a single-cipher delete, but it does not differentiate among the many near-duplicate siblings such as delete_cipher_selected_post, _put, or _admin.

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 description implies bulk deletion but gives no explicit guidance on when to use this tool versus the singular delete_cipher or the numerous post/put/admin variants. No conditions, prerequisites, or alternatives are named.

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