merge_memories

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

Adds atomicity, one-shot nature, and dedup details beyond annotations (destructive hint, idempotent hint). Clarifies that 'move' mode deletes source data.

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 concise, front-loaded sentences: core purpose first, then atomicity and strategy nuance. No wasted words.

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?

Covers purpose, atomicity, and strategy detail. No output schema, but description doesn't need to explain returns. Missing error handling or prerequisites, but adequate for a merge tool.

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%, but description adds specific dedup criteria (msg_id for memories, summary for episodes) for the strategy parameter, enhancing schema info.

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 clearly states it merges memories, episodes, and profiles from one agent into another, and distinguishes from export→import by being atomic and file-less.

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?

Implied usage as an alternative to export+import, but no explicit when-to-use, when-not, or guidance on selecting between merge and the export/import siblings.

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