forget

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

With no annotations, the description carries the burden of behavioral disclosure. The word 'Delete' clearly indicates destructive behavior, but the description does not disclose irreversibility, audit trail implications, or any side effects. It is not misleading, but lacks rich context.

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 concise sentence followed by a usage note. It is front-loaded with the action and object, with zero 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?

For a simple delete tool with fully documented parameters and no output schema, the description covers purpose, scope, and a usage condition. It lacks only explicit mention of return value or side effects, but these are not critical for this tool's simplicity.

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 input schema fully covers both parameters (memoryId and reason) with descriptions, so the baseline is 3. The tool description does not add additional parameter information beyond what the schema provides.

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 clearly states the tool deletes a memory by ID, using the specific verb 'Delete' and identifying the resource. This distinguishes it from sibling tools like remember, recall, and list_memories.

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?

The description explicitly says 'Use when information is outdated or incorrect,' providing a clear context for when to invoke this tool. It does not explicitly list alternatives or exclusion criteria, but the guidance is sufficient for a simple deletion action.

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