mcp_engram_forget_old

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

Discloses that pinned blocks (CRS=1.0) are always exempt, and older_than_days targets stale memories while preserving recent ones. Given no annotations, description carries full burden and does well.

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, front-loaded with action, uses clear sections (WHEN TO USE), no redundant words. Every sentence adds value.

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?

Self-contained: explains purpose, usage, behavioral exemptions, parameter tips, and references preview tool. No critical gaps for an agent to use correctly.

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 covers both parameters (100% coverage). Description adds usage guidance: suggests starting threshold at 0.3 (vs default 0.2) and explains purpose of older_than_days for preserving recent memories.

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?

Description uses specific verb 'evict' and resource 'non-pinned memories below a CRS threshold', clearly distinguishing it from siblings like mcp_engram_forget. The metaphor 'autophagy' adds context.

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?

Explicit 'WHEN TO USE' section lists concrete scenarios (end of project phase, after distill runs, manifold too large). Provides conservative starting threshold and recommends previewing with mcp_engram_stats.

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