mnemos_delete

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

The term 'soft-delete' adds value beyond annotations by indicating the operation marks data as deleted without immediate removal. However, no further behavioral details (e.g., reversibility, permission requirements, or state changes) are disclosed.

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 phrase with no wasted words. It is front-loaded and efficient for its length.

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 one-parameter tool with a soft-delete behavior and no output schema, the description is adequate but lacks depth—e.g., it does not clarify how a soft-deleted memory can be recovered or whether this affects search results.

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 'id' is already documented. The description adds no additional meaning beyond what the schema provides, earning a baseline score of 3.

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 'Soft-delete a memory' uses a specific verb ('soft-delete') and a clear resource ('memory'), making its purpose distinct from sibling tools like mnemos_store or mnemos_get. No ambiguity.

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 soft-delete versus alternatives (e.g., permanent deletion, updates, or other operations). The description lacks context for choosing this tool over siblings.

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