forget

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It adds the guardrail 'Do not auto-forget,' but does not disclose that deletion is irreversible or that the filter parameter can delete multiple entries at once. The confirmation requirement is left to the schema.

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 short sentences, front-loaded with the core action and followed by a crucial usage constraint. 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?

The description is minimally viable but lacks important context for a destructive tool: it does not mention that deletion is permanent, that filter can delete many entries, or that confirm=true is required. The schema covers confirm, but given no annotations and an output schema, the description could do more to ensure safe invocation.

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 description adds no parameter-level detail; it only says 'specific memory entries,' which vaguely hints at id/filter selection. The input schema already covers the parameters with descriptions (67% coverage), so the description does not enhance understanding of how to choose between id and filter or how confirm works.

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 'Delete specific memory entries' with a specific verb and resource, clearly distinguishing this from sibling tools like recall, search, and capture. The scope is clear and unambiguous.

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 this tool only when the user requests a deletion. Do not auto-forget.' This provides both a clear condition for use and a prohibition against unsolicited deletion, which is excellent guidance.

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