Remember

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

Annotations indicate openWorldHint=true and readOnlyHint=false. The description adds valuable behavioral context: 'Vector search indexing completes asynchronously within a few seconds after save.' This goes beyond what annotations provide. No contradiction detected.

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 three sentences: first states purpose, second gives usage tips, third explains async indexing. No unnecessary words. Every sentence adds value. Front-loaded with purpose.

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's complexity (9 parameters, 1 required) and that output schema exists, the description covers key aspects: purpose, collection naming convention, append_to dedup, and async behavior. It is complete enough for an agent to invoke correctly without additional context.

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 description coverage is 100%, so baseline is 3. However, the description adds meaning beyond schema: e.g., 'Always set collection when the topic is clear: project work → project:<slug>, personal tastes → personal:preferences' and 'Use append_to to extend an existing memory instead of creating duplicates.' This provides strategic guidance on parameter usage.

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 'Save important information to long-term memory', which is a specific verb+resource. It distinguishes from sibling tools like forget, get_memory, and recall, and provides additional context on when to set collection and use append_to.

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 explicit guidance on when to set collection and when to use append_to to avoid duplicates. It also mentions asynchronous indexing behavior. It does not explicitly state when not to use the tool, but the context is sufficient for an agent to decide.

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