backlog_forget

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

No annotations provided, so description carries full burden. Discloses soft-expire vs hard-delete, audit trail, and GC mode. Lacks idempotency and auth details, but sufficient for core behavior.

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 sentences with purpose, usage, and GC note. Front-loaded with action and effect. 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?

Given 7 boolean/string params, no output schema, and no annotations, description covers core behavior and parameter usage. Missing return value info but typical for forget action. Adequate for tool selection.

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 100% (baseline 3). Description adds meaningful context: 'ids' as MEMO- ids, 'home' as document home override, 'layer' as memory layer, 'context' with example, 'expired' as GC mode, 'older_than' with ISO date, 'project_root' as override. Provides value beyond schema.

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?

Clear verb 'retract' and 'soft-expire', resource 'memories', effect 'recall stops returning, record stays auditable'. Distinguishes from sibling backlog_remember with supersedes.

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 when to use (knowledge wrong/obsolete, no replacement) and when not to (if replacement exists, use backlog_remember with supersedes). Also explains expired:true GC mode.

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