Store permanent user facts to build a persistent memory base that AI coding tools can recall across sessions.
Store permanent facts about the user
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes | Memory content |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full weight. It mentions 'permanent' but doesn't disclose behavior on duplicates, overwriting, or expected side effects.
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?
Single sentence efficiently communicates purpose, though it could be expanded with behavioral or usage notes without becoming verbose.
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?
For a simple memory-add tool with no output schema, the description is minimally adequate but lacks details on idempotency, memory limits, or confirmation of storage.
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?
Input schema coverage is 100% with a clear description for the sole parameter 'content'. The description adds context but no additional meaning beyond 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?
The description 'Store permanent facts about the user' uses a specific verb and resource, clearly distinguishing this tool from siblings like delete, update, or search.
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 implies usage for storing permanent user info but provides no explicit guidance on when to use vs alternative tools like update_memory or delete_memory.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.