Permanently delete your note using data.expected_version from a fresh read. No version history or undo is provided by the API. Private to this agent identity.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Stable private note name, scoped to the authenticated agent. | |
| data | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| replayed | No | ||
| operation | No | ||
| truncated | No | ||
| next_cursor | No |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "description": "Structured result for delete_memory. Resource fields vary by detail, permissions and operation. Paginated results use items/next_cursor; operation-key replays use operation/replayed. Failures have error and the MCP result has isError=true. See get_help for this tool's contract.",
+ "properties": {
+ "error": {
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "help": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ },
+ "next_action": {
+ "type": "string"
+ },
+ "retry_after_seconds": {
+ "type": "integer"
+ }
+ },
+ "required": [
+ "code",
+ "message",
+ "next_action",
+ "help"
+ ],
+ "type": "object"
+ },
+ "next_cursor": {
+ "type": "string"
+ },
+ "operation": {
+ "type": "object"
+ },
+ "replayed": {
+ "type": "boolean"
+ },
+ "truncated": {
+ "type": "boolean"
+ }
+ },
+ "type": "object"
+}Input schema / properties / data / properties / operation_keyAdded value: +{
+ "description": "Optional stable client key scoped to this agent for 30 days. Reuse identical payload after a timeout. Different payload conflicts. Retry returns compact operation receipt, not original body. Distinct from diagnostic request_id; existing create-space request_id remains required.",
+ "maxLength": 80,
+ "pattern": "^[a-z0-9]+(-[a-z0-9]+)*$",
+ "type": "string"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description goes beyond the destructiveHint annotation by disclosing permanence, the absence of version history/undo, and scoping to the agent identity. These are important behavioral details that an agent could not infer from the schema alone.
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 tight sentences front-load the core action and permanence, then add the critical precondition and identity scoping. Every sentence earns its place with no filler.
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 is complete for a destructive tool: it warns about irreversibility, explains the required version check, and scopes the operation. The output schema exists, so return-value details are not needed here.
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 top-level description only addresses expected_version and ignores operation_key, despite low schema coverage of 50%. The schema itself documents both parameters, but the description adds little beyond restating the fresh-read requirement already present in 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 names a specific verb ('delete'), a clear resource ('your note'), and the required precondition ('using data.expected_version from a fresh read'). It is immediately distinguishable from siblings like restore_memory and save_memory.
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?
It gives explicit guidance on how to use the tool: call after a fresh read and supply the current expected_version. It warns about no undo, which discourages casual use. It does not explicitly name alternatives or state when not to use it, but the context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.