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

The annotations already mark destructiveHint=true, and the description goes well beyond that by explaining that it clears memory, causes a fresh engager fetch for every forgotten post, and affects only competitor_posts and post_engagers. It also warns about post_engagers being RETIRED, which is important behavioral context not visible from annotations alone. 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?

The description is longer than average, but every sentence earns its place: it explains the problem being solved, the mechanism, the cost, and the exact invocation condition. It is front-loaded with the core purpose ('The tuning escape hatch') before diving into mechanics, and the cost warning is placed before the usage rule.

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 destructive mutation tool with no output schema, this description covers what is needed: what memory is cleared, why it matters, what it costs, when to call it, and which lanes are affected. The input schema fully documents the parameters, so nothing an agent needs to correctly invoke this tool is missing.

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%, and the schema already provides detailed parameter descriptions, including the full enum and per-value explanations. The tool description adds the useful context that only competitor_posts and post_engagers actually have the memory being cleared, but it does not need to repeat parameter details since the schema covers them.

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 ('forget') and resource ('harvested posts' / post lane memory), and explains the exact effect: clearing the memory so the next run re-judges posts. It differentiates itself from sisters by framing itself as 'the tuning escape hatch for the post lanes' and noting that only competitor_posts and post_engagers have this memory.

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 is explicit about when to call it: 'Call it only after a deliberate settings change the human wants re-tested.' It also gives a strong why—without this, tuning is impossible because the lane remembers already-harvested posts—and a strong caution: 'every forgotten post is a fresh engager fetch.' That is clear decision guidance, including the cost of misuse.

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