import_memories

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

Annotations indicate it's not read-only and not destructive, but the description lacks details on behavioral traits such as whether the import overwrites existing data, what the 'merge' mode entails, or any error handling. It adds minimal value beyond the annotations.

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 extremely concise: two sentences plus an action guide with an example. It is front-loaded with the main action and structured efficiently.

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 2 parameters and 0% schema coverage, the description provides a usage example but misses behavioral details like what the tool returns (despite an output schema existing) and how modes other than 'merge' behave. It is adequate but not thorough.

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?

With 0% schema description coverage, the description provides an example showing 'data' as a JSON string and 'mode' as 'merge', adding some meaning. However, it doesn't explain other possible values for 'mode' or the format of the data array, so the compensation is partial.

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 'Import memories from JSONL data or a list of objects', specifying the verb 'import' and the resource 'memories', which distinguishes it from siblings like 'add_memory' or 'export_memories'.

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 includes an explicit 'ACTION GUIDE — when to use' section: 'Use when restoring from a backup or migrating data into the memory system', providing clear context for usage. It does not mention when not to use, but the guidance is strong.

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