Delete a secret from the team vault by providing its name and passphrase. Removes sensitive data from the encrypted SQLite store.
Delete a secret from the team vault.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name of the secret to delete | |
| passphrase | Yes | Team vault passphrase |
Changes observed during successful MCP inspections.
v0.9.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It says the tool deletes a secret, implying a destructive mutation, but does not describe irreversibility, permission requirements, failure modes, or whether deletion is permanent.
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 a single front-loaded sentence with no wasted words. It is efficient, though its brevity reflects under-specification rather than optimal conciseness.
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 destructive mutation tool with no annotations and no output schema. The description does not explain what happens on success or failure, whether deletion is reversible, or what permissions the passphrase grants. For a team-vault deletion operation, that leaves important context missing.
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 100%, and both parameters are clearly documented in the schema. The description adds no additional parameter meaning beyond the schema, so the baseline of 3 is appropriate.
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: delete a secret. It also scopes the resource to the team vault, which helps distinguish it from sibling tools like delete_secret. However, it does not explicitly name alternatives or state that it is not for non-team secrets.
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 provides no guidance on when to use this tool versus alternatives such as delete_secret or team_resolve. It does not mention prerequisites, exclusions, or the required passphrase context beyond what the schema already states.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.