Delete Memory

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

With no annotations, the description carries full burden for disclosing behavior, but it only states the destructive intent and repeats the parameter hint. It does not clarify whether deletion is permanent, what happens if multiple entries match, or whether a failure to find the fragment results in an error or no-op.

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 two short sentences with no filler, front-loading the operation and then the key usage requirement. Every word contributes to the core message, making it appropriately concise.

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 tool is simple with one required parameter and a fully documented schema, so minimal description is acceptable. However, since no annotations or output schema exist, the description omits useful context about side effects, matching behavior, and how to locate the fragment, leaving some room for agent uncertainty.

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 the baseline is 3. The description adds the word 'unique' beyond the schema's 'distinctive part,' slightly strengthening the matching requirement, but it does not provide substantial new meaning beyond what the schema already offers.

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 clear verb and resource ('Delete something from memory') and the unique-fragment requirement distinguishes it from sibling operations like read, save, or update. It is somewhat vague about what 'memory' contains, but the action and target are unmistakable.

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 explicit guidance is given for when to use delete_memory versus alternatives such as update_memory or tidy_memory. The instruction to provide a unique fragment is a how-to hint rather than a when-to-use explanation, leaving the agent to infer the appropriate scenario.

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