Delete all stored memories for a specific actor to clear their history. Use this to permanently remove an actor's data when it is no longer needed.
Delete ALL memories belonging to a specific actor. Irreversible.
| Name | Required | Description | Default |
|---|---|---|---|
| actorId | No | Actor ID to purge. Defaults to the current session actor. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full responsibility for behavioral disclosure. It explicitly states the operation is irreversible and deletes all memories for an actor, which is important destructive behavior. However, it does not mention other side effects such as confirmation, cascading behavior, or impact on related data.
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 extremely concise, using two short sentences with no filler. The critical information—destructive scope and irreversibility—is front-loaded and clearly stated.
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 tool's simple action and the absence of an output schema, the description provides enough contextual information to understand the core behavior. It could be slightly more complete by mentioning what happens to the actor after purging or any return value, but the essential context is present.
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 input schema provides 100% coverage for the single parameter, including its default behavior ('Defaults to the current session actor'). The tool description adds no additional parameter semantics beyond the schema, so the baseline score applies.
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 clearly states the action ('Delete'), the target ('ALL memories'), and the scope ('belonging to a specific actor'). The word 'ALL' and 'Irreversible' make the destructive scope unambiguous.
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 guidance is provided on when to use this tool versus related sibling tools such as memory_delete, memory_delete_many, or memory_prune. The description does not mention conditions, alternatives, or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
This server cannot be deployed