Delete a stored memory by key and optional namespace or pool scope to remove outdated or unwanted entries from the Mullet memory store.
Delete a memory by namespace and key.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Key of the memory to delete | |
| namespace | No | Namespace of the memory (default: mcp) | |
| pool_name | No | Pool scope (optional, global if omitted) |
Changes observed during successful MCP inspections.
v2.4.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It says "Delete" but does not disclose whether deletion is permanent, what permissions are required, whether the operation is reversible, or how pool scope affects deletion.
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 states the action and the primary identifiers efficiently.
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?
For a low-complexity tool with full schema coverage and no output schema, the description is minimally adequate. However, as a delete operation with no annotations, it should provide more context about irreversibility or safety implications.
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%, so the input schema already documents key, namespace, and pool_name. The description mentions namespace and key but adds no syntax, default, or scope details beyond the schema.
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 memory by namespace and key." It is clear which operation this tool performs, though it does not explicitly distinguish itself from sibling tools such as trawl_memory_store or trawl_memory_search.
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 like trawl_memory_store, trawl_memory_search, or trawl_memory_list. It only states the operation, leaving usage context implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.