forget

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

With no annotations, the description must carry behavioral disclosure. It states 'Delete' indicating destructiveness, but does not detail permanence, reversibility, authorization requirements, or effects on other users. This minimal transparency leaves the agent unaware of important behavioral traits.

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 consists of two front-loaded sentences: the first states the primary action, the second provides a key constraint. Every word serves a purpose, with no redundancy or filler. It is appropriately sized for a simple deletion tool.

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?

Given the destructive nature (no annotations) and three optional parameters, the description is insufficient. It does not clarify what happens if no filter is provided, whether deletions are cascading, or if confirmation is needed. An output schema exists but return values are not described. The brief text leaves significant gaps for an AI agent.

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% with each parameter described (tags, project, memory_ids). The description adds only the general constraint 'Specify at least one filter criterion,' which does not enhance understanding beyond the schema. Baseline 3 is appropriate as the schema already documents parameters well.

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 'Delete stored memories,' which specifies the verb (delete) and resource (stored memories). It distinguishes from sibling tools (list_memories, recall, remember) by being the deletion tool. However, it could be more specific about what 'stored memories' encompasses (e.g., user-specific or global).

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 provides a constraint ('Specify at least one filter criterion') but offers no guidance on when to use this tool versus alternatives like list_memories or recall. It does not explain scenarios for deletion, prerequisites, or consequences.

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