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

Annotations already flag destructiveHint=true, but the description goes further by disclosing what is actually destroyed (the source facts), that creation and deletion are atomic, and that nothing is written until confirm_action is called. The proposal/confirmation handshake with action_id and plan_token is behavioral context the annotations cannot express.

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 tight sentences plus a labeled CONFIRMATION block, with the purpose and the argument mapping front-loaded and the exceptional control flow quarantined in its own section. No redundant restatement of the title.

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, two-phase write tool with no output schema and no schema descriptions, the definition covers what it does, what it consumes, what it deletes, and how confirmation gates execution. Nothing an agent needs in order to call it correctly or safely 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 0%, so the description carries the burden, and it does define all three inputs in prose: source_ids are 'the facts to replace', content is 'the new content', tags are optional. It does not explain the 200-item cap, the mixed integer/string id types, or how ids of different types are matched, so it falls slightly short of full compensation.

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?

States a specific verb and resource plus the exact shape of the operation: 'Merge SEVERAL duplicate/older memory facts into one clean fact'. It also distinguishes itself from the N-separate-writes alternative ('without N separate forgets'), so an agent can place it against forget_memories and confirm_action without opening a schema.

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 frames the trigger condition ('the natural collapse N versions into one workflow') and the alternative it replaces (N separate forgets). It also states the mandatory follow-up path — call this, receive status='confirmation_required' with action_id and plan_token, then use confirm_action — which is exactly the when/what-next guidance an agent needs.

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