create_memory

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

No annotations are provided, so description must fully disclose behavior. It states 'durable' and 'survive beyond current chat', but lacks details on side effects, error handling, or prerequisites. For a write operation, this is insufficient.

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, clear, and to the point. No unnecessary words. Could be slightly more front-loaded with the key verb 'create' already prominent.

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 complexity of the memory system (18 sibling tools), the description is too minimal. It does not mention output schema existence, relationship to other tools, or provide enough context for an agent to understand when this specific creation tool is appropriate compared to others.

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 coverage is 100%, so baseline is 3. The description adds no new parameter information beyond what the schema already provides. It does not repeat or enhance meaning, but also doesn't detract.

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?

Description clearly states it creates a durable markdown memory for facts, decisions, preferences, or project context. The verb and resource are specific. However, it does not explicitly differentiate from sibling tools like 'remember' or 'record_trace', which may also create persistent notes.

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 explicit guidance on when to use this tool versus alternatives. Description implies it's for durable content, but does not mention when not to use it or point to siblings for other operations (e.g., append, update, search).

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