merge_memories

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

Annotations indicate non-read-only, non-destructive by default, and idempotent. Description adds atomicity and deduplication behavior but fails to disclose that 'move' mode is destructive on source or permissions needed.

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?

Three concise sentences, each adding value. Front-loaded with main action, no redundant 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?

Covers key points but omits explanation of 'copy' vs 'move' modes, dry run behavior, and return value. Given no output schema, some return expectation would improve completeness.

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?

100% schema coverage provides solid baseline. Description adds meaningful context for 'strategy' by specifying deduplication fields (msg_id for memories, summary for episodes), which is not in schema.

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 merging memories, episodes, and profiles from one agent to another. Differentiates from sibling tools like export_memories and import_memories by describing it as an atomic one-shot equivalent without intermediate files.

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?

Explains when to use the strategy 'skip' for deduplication and positions as an alternative to export-import, but does not discuss when to choose between 'copy' and 'move' modes or provide explicit conditions for use versus non-use.

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