import_memories

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

Annotations indicate readOnlyHint=false (write operation) and destructiveHint=false (not destructive), but the description adds minimal behavioral context. It does not explain what happens on import (e.g., merge vs replace, duplicate handling, atomicity), leaving significant gaps.

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 very concise: one sentence for purpose, then a structured action guide with bullet and example. No wasted words, front-loaded, and easy to scan.

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 2 params and an output schema, the description covers the basic use case but lacks detail on mode options and data format. For a data import tool, more completeness on parameters and behavior is expected.

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 0%, so description must compensate. It adds meaning by specifying 'data' can be JSONL or list, and gives an example with mode='merge'. However, it does not explain valid modes or object structure, leaving ambiguity.

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 imports memories from JSONL data or a list of objects, and the action guide specifies it is for restoring backups or migrating data. This distinguishes it from the sibling 'add_memory' for single additions, but does not explicitly compare them.

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 action guide explicitly recommends use for restoring or migrating data, providing clear context. However, it does not mention when not to use or compare with alternatives like 'add_memory' for single entries.

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