Restore cipher selected

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

Annotations already declare this is not read-only, not destructive, and open-world. The description adds only 'bulk' and 'from trash', without explaining what happens to restored items (e.g., folder placement), permission requirements, or whether the operation is reversible.

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 only four words and front-loaded, but it is under-specified rather than appropriately concise. It omits essential context that an agent needs to invoke the tool correctly.

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 mutating bulk-restore operation with three completely undocumented parameters, no output schema, and only minimal annotations. The description does not compensate for the schema's opacity or provide enough context to call the tool safely and correctly.

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?

The schema has three parameters (form, params, json_body) with 0% description coverage, and the description provides no information about them. For a bulk selection tool, the agent needs to know how selected cipher IDs are supplied; neither schema nor description clarifies this.

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 (restore) and scope (bulk from trash), so the broad action is understandable. However, it does not name the resource (ciphers) or distinguish this tool from sibling variants such as restore_cipher_put, restore_cipher_put_admin, and restore_cipher_selected_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 gives no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. It only implies usage by saying 'from trash'.

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