forget

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

Since no annotations provided, description fully discloses destructive nature (destroys thermodynamic history: CRS, Merkle chain, ADR state). Warns about permanence and pinned block behavior. No contradiction with annotations.

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?

Well-structured with clear warnings and usage guidelines. Each sentence adds value; no redundancy. Efficiently conveys critical 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?

For a single-parameter destructive tool, description covers purpose, when to use, behavioral consequences, and alternative. Lacks mention of other siblings like mcp_engram_forget_old but does not detract significantly. Output schema not needed.

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?

Only one parameter (concept) with schema description 'The concept name to delete'. Description does not add further detail beyond schema; overall context implies concept is a memory block but no additional constraints or format guidance.

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?

Clearly states the action (permanently delete) and resource (memory block from manifold). Distinguishes from sibling mcp_engram_update by contrasting deletion vs. updating.

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 (obsolete concept or stored in error) and when not (use update instead). Also covers edge case of pinned blocks (CRS=1.0).

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