memory_store

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

With no annotations provided, the description carries the full transparency burden. It discloses the primary side effect (storing a new memory), the edge-creation behavior, legacy behavior of 'related_to', and notes that 'possible_conflicts' may be returned as heuristic hints. It does not mention authentication or permission side effects, but the core behaviors are transparent.

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 concise, using only two sentences to cover purpose, edge semantics, legacy behavior, and return hints. There is no redundancy or unnecessary detail.

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?

The description covers the essential purpose, key parameter distinctions, legacy behavior, and return hints. It omits some details about fields like 'content' and 'visibility', but the overall context is sufficient for a typical agent to correctly invoke the 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?

The description adds value by explaining 'related' edges, the legacy nature of 'related_to', and the direction semantics. However, schema coverage is only 57%, and the description does not compensate for undocumented parameters like 'content', 'visibility', or 'source_session'. It partially clarifies parameters but not comprehensively.

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 clearly states the tool's primary action: storing a new memory in the causal memory graph. It distinguishes itself from sibling tools like memory_amend (existing memories), memory_recall, and memory_search by emphasizing 'new 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 gives clear context for using the tool, including guidance on preferring the 'related' parameter over the legacy 'related_to' and clarifying that 'related_to' always creates caused_by edges. It does not explicitly say 'use this instead of memory_amend for existing memories,' but the context is clear enough.

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