import_memories

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

Since no annotations are provided, the description carries the full burden, and it does add the duplicate-handling behavior (skip/bump/replace), which is relevant context. It does not define what "bump" means, whether the import merges with existing memories or replaces the whole store, or what happens on invalid JSON.

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?

Two short sentences with no filler: the verb, resource, and source format are front-loaded, and the on_duplicate line is compact. Every phrase earns its place.

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 only two parameters and a reasonable schema, this is close to adequate, but the lack of annotations and output schema makes the missing details more costly. An agent still doesn't know whether the import is additive or destructive, what counts as a duplicate, or what the tool returns.

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?

The schema already describes the data parameter's shape, and the description only restates on_duplicate's allowed values without explaining their semantics, especially "bump." With 50% schema coverage, the description adds modest value but doesn't fully compensate for the missing parameter-level explanation.

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?

States a specific verb (import), resource (memories), and source format (JSON), and mentions the on_duplicate policy, which gives useful differentiation from related tools. It doesn't explicitly contrast with sibling tools like remember or export_memories, but the import-from-JSON framing makes the core purpose clear.

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 phrase "Import memories from JSON" implies this is the tool to use when you have memory data in JSON format to load, and the on_duplicate options give situational choices. However, there is no explicit statement of when to prefer this over remember or export_memories, nor any exclusionary guidance.

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