import_memories

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'batch import' and references an export tool for format, but lacks critical details: whether this operation overwrites existing memories, requires specific permissions, has rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 highly concise and front-loaded, consisting of two sentences that directly convey the tool's purpose and usage without any wasted words. Every sentence earns its place by providing essential information about the operation and format reference.

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 an output schema (which reduces the need to describe return values) but no annotations and low schema coverage, the description is moderately complete. It covers the basic purpose and format, but lacks details on behavioral traits, error handling, and parameter semantics, making it adequate but with clear gaps for a mutation tool.

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 input schema has 1 parameter with 0% description coverage, so the description must compensate. It adds value by specifying the parameter 'data' should be a JSON string in a particular format and referencing 'export_memories' for examples. However, it doesn't explain the semantics of fields like 'content', 'tags', or 'source', or provide validation rules, leaving gaps in understanding.

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's purpose: 'Import memories from a JSON string (batch import).' It specifies the verb ('import'), resource ('memories'), and scope ('batch import'), distinguishing it from sibling tools like 'export_memories' or 'list_memories'. However, it doesn't explicitly differentiate from 'import_conversations' or 'import_from_ai', which are similar import operations.

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 provides clear context for when to use this tool by referencing 'export_memories to get the expected format,' indicating it's for batch imports of memories in a specific JSON structure. It implies usage for data migration or restoration scenarios. However, it doesn't explicitly state when not to use it or compare it to alternatives like 'import_conversations'.

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