backlog_forget

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

Explains soft-expiration and that records remain auditable. Describes GC mode for expired memories. Lacks details on permissions or side effects, but given no annotations, it adequately covers key 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?

Concise and front-loaded: first sentence states core purpose. Three short sentences total, each adding critical information without fluff.

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?

Adequately explains behavior, usage, and one key parameter. Lacks description of return values or error handling, but given the tool's simplicity, it is mostly complete.

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% so baseline is 3. Description adds value by explaining the 'expired' parameter in detail ('GC mode: hard-delete memories that are already expired'). Other parameters are already well-described in 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?

The description clearly states the tool's purpose: 'Retract memories — soft-expire them so recall stops returning them'. It also distinguishes from siblings by specifying when to use backlog_remember instead.

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: 'when knowledge is wrong or obsolete and there is no replacement'. Provides a clear alternative: 'if there IS a replacement, use backlog_remember with supersedes instead'.

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