Move a password to the trash for reversible deletion, restorable from the Passwords app. Refuses already-trashed entries to prevent permanent deletion.
Move a password to the trash (a reversible, soft delete — restore it from the Passwords app). Refuses if the entry is already trashed, so it can never permanently delete anything.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Id of the password to trash. |
Changes observed during successful MCP inspections.
v0.3.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description fully discloses the side effect (soft delete to trash) and explicitly states it can never permanently delete anything. It also mentions the refusal condition for already-trashed entries, going beyond the annotation flags.
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?
Two concise sentences, no redundant information, and the key points are front-loaded. Highly efficient and readable.
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?
Given the simple action and no output schema, the description covers all necessary aspects: action, reversibility, edge case, and guarantee of non-permanence. No missing context for an agent to invoke it 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 only parameter 'id' is clearly documented in the schema as 'Id of the password to trash', and the description consistently references it. Full parameter coverage with no ambiguity.
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?
Description clearly states it moves a password to trash as a reversible soft delete, distinguishing it from any permanent deletion. It specifically identifies the action and resource.
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?
Description explains the behavior and edge case (refuses if already trashed), making it clear when to use this tool. It also implies the alternative restore process via the Passwords app, aligning with sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.