memory_forget

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

Discloses destructive side effect, irrecoverability, and idempotence. With no annotations, the description fully covers behavioral traits needed for safe invocation.

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?

Well-organized into sections with clear headings (USAGE, BEHAVIOR, PARAMETERS). Every sentence adds value; no wasted words.

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?

Covers purpose, usage, behavior, parameter semantics, and return values (confirmation of deleted key and existence check). For a single-param tool, this is fully complete.

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?

For the single parameter 'key', the description adds context: 'exact key as passed to memory_store', 'Case-sensitive', and 'Required'. With 0% schema description coverage, this fully compensates.

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 starts with 'Delete a memory entry by exact key', which clearly specifies the action and target. This distinguishes it from sibling tools like memory_store (store) or memory_list (list).

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 states 'USE WHEN: a stored value is wrong or no longer needed' and 'NOT FOR: clearing all memory', with guidance to loop over memory_list. Provides clear when-to-use and when-not-to-use.

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