Soft-delete XMemo memory

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description adds 'recoverable' (soft delete) beyond the destructiveHint annotation, providing important behavioral context. No contradiction.

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 sentences, no filler. Front-loaded with action and conditions. Every sentence earns its place.

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?

Addresses purpose, usage, and key behavioral trait (recoverable). Sufficient for a tool with rich schema and annotations. Could mention other modes briefly, but not necessary.

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 coverage is 100%, so description need not repeat. But description adds context that 'mode' default aligns with soft-delete behavior, and 'memory_id' is exact reference. Good complement.

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 deletes a memory in a recoverable manner by exact reference, and distinguishes from siblings 'forget' and 'delete_current_memory' which are for permanent deletion.

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?

Explicitly says when to use: when user asks to remove or hide a memory. Also specifies alternatives for permanent deletion (forget, delete_current_memory).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.