Delete a memory from the selected scope, allowing later restore through the maintenance CLI.
Soft-delete a memory in the selected scope. Restore is available through the maintenance CLI.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| project | No | ||
| namespace | No | ||
| include_deleted | No |
Changes observed during successful MCP inspections.
v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
While annotations indicate idempotent and non-destructive, the description clarifies it is a soft-delete and mentions that restore is available via maintenance CLI, adding useful behavioral context beyond annotations.
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?
Short, single-sentence description with no unnecessary fluff.
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?
The description fails to provide enough context for correct usage, such as what 'selected scope' means, which parameters are needed, and what happens to linked data. The restore note helps but doesn't compensate for missing parameter explanations.
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 description does not explain any of the four parameters (id, project, namespace, include_deleted). 'Selected scope' is vague and doesn't map to parameters.
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?
Clearly states it soft-deletes a memory, with a specific verb and resource. Also mentions restore via maintenance CLI, providing useful context.
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 explicit guidance on when to use this tool over alternatives like memory_update or memory_remove. The mention of restore is about recovery, not about usage scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.