add_memory

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

With no annotations, the description must disclose behavioral traits itself. It only states that it stores a memory, but doesn't clarify whether it overwrites, appends, requires specific permissions, or what side effects occur. The word 'new' implies no overwriting but leaves other behaviors undisclosed.

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 a single sentence with no filler, but it is almost too terse, offering minimal substance. It is concise and front-loaded, more efficient than verbose, though it trades away helpful context.

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?

Given the tool has a complete schema and no output schema, the description covers only the basic action. It lacks usage context and behavioral caveats, but the schema mitigates some gaps. Overall, it is a minimally viable description for a straightforward create operation, but leaves room for improvement.

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?

The input schema covers all three parameters with descriptions (content, user_id, metadata), achieving 100% schema coverage. The description adds no additional parameter semantics, so the baseline score of 3 applies.

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 uses the specific verb 'Store' targeting 'a new memory in Mem0', clearly distinguishing this write operation from sibling tools (search_memories, get_memories, delete_memory). The phrase 'new memory' confirms an insert action, leaving no ambiguity about its core function.

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?

No guidance is provided regarding when to use this tool versus alternatives. The description does not mention that this is for creating memories, while search/get/delete are for reading/removing, nor does it note any prerequisites or edge cases like duplicate handling.

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