import_memories

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

The description adds idempotency via msg_id deduplication, which aligns with the idempotentHint annotation. However, the destructiveHint=true annotation is not explained, and the description does not clarify potential destructive behavior or side effects.

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 sentences, front-loaded with the main action, and no unnecessary words. Every sentence contributes essential information.

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?

For a bulk import tool, crucial details are missing: expected JSONL structure, error behavior, return values (no output schema), and what 'destructive' means. More context would improve usability despite good annotations.

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 has 100% parameter descriptions, so the tool description adds no extra parameter-level meaning. The global behavior (idempotent, JSONL format) is mentioned but not per-parameter.

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, episodes, and profiles from a JSONL file, with specific verb and resource. It distinguishes itself from siblings like store (single record) and update_memory (update) by targeting bulk import.

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?

No explicit guidance on when to use this tool vs alternatives (e.g., store, update_memory). The description only states what it does, not when it is appropriate or what to avoid.

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