import_conversations

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

With no annotations, the description discloses that messages are normalized and stored via the standard persistMemory pipeline, and that format auto-detection is available. This provides useful process context, though it does not address error handling or side effects, meriting a 4.

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 three sentences, front-loaded with the primary purpose and lists formats efficiently. Every sentence earns its place, with no redundant information, earning a 5.

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?

The tool has no output schema, and the description does not explain return values or error scenarios, which is a notable gap for an import tool. However, the description does cover the input formats and processing pipeline, so for moderate complexity it scores a 3.

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 already provides detailed descriptions for all three parameters, achieving 100% coverage. The description adds minimal semantic value beyond the schema, only mentioning the explicit format parameter and connector spec reference, so the baseline 3 is appropriate.

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 conversation files into memory and lists supported formats. It is specific about the resource and action, but does not explicitly differentiate from siblings like store_memory or batch_store, so it earns a 4.

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 implies usage for importing conversation files in specific formats but does not explicitly state when to use this tool over alternatives or when not to use it. There are no exclusions or alternative tool mentions, so it scores a 3.

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