Hard purge memory

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

In the absence of annotations, the description discloses key behaviors: the tool can preview or permanently remove records, and it creates a backup before an applied purge. It does not, however, detail the permanence of removal or the recovery process from backup, but overall transparency is good.

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 sentences: the first states the purpose, the second adds a critical behavioral detail (backup). It is front-loaded, efficient, and contains no redundant information.

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?

With 6 parameters, no output schema, and no annotations, the description is too brief. It does not explain what the preview returns, behavior with no matching records, the backup process, or constraints on filters. More detail is needed for adequate completeness.

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 description coverage is only 17% (only 'confirm' has a description). The tool description adds the concept of 'matching records' to imply filtering, but it does not explain the semantics or formats of the other five parameters (id, tags, before, source, namespace). This leaves significant ambiguity for the agent.

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 specific verb-resource pair ('Preview or permanently remove matching records from the canonical store') making the tool's core action clear. However, it does not explicitly distinguish itself from sibling tools like 'delete_memory' or 'compact_memory', which may have overlapping functionality.

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 implies a two-step workflow (preview with confirm=false, apply with confirm=true) but provides no explicit guidance on when to use this tool over alternatives (e.g., delete_memory) or conditions to avoid using it. No exclusions are mentioned.

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