memory_import

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

The description discloses behavioral details such as rate limiting and the effects of each strategy (clear all, skip duplicates, add all). However, since no annotations are provided, the description carries the full burden. It lacks information on error handling, validation behavior for invalid data, or whether the operation is idempotent, which are important for a mutation tool.

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 at two sentences plus an Args block, with no extraneous information. Every sentence serves a purpose: stating functionality, rate limit, and parameter semantics. It is well-structured and front-loaded.

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 presence of an output schema (not shown) and the tool's complexity (bulk import with different strategies), the description is fairly complete but lacks guidance on error cases, response format, or prerequisites (e.g., required auth). It covers the essential inputs but could be more 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?

The input schema has 0% coverage (no parameter descriptions in JSON schema), so the description adds significant value by explaining that 'data' expects a list of memory dicts with specific keys (content, metadata, tags, created_at) and 'strategy' is one of three enumerated values. This compensates well for the schema gap.

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 from JSON format, using a specific verb ('import') and resource ('memories'). This distinguishes it from sibling tools like memory_create or memory_create_batch, which are for creating individual memories rather than bulk importing.

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 mentions a rate limit (60s cooldown) and explains the three strategies ('replace', 'merge', 'append'), providing context on when each might be used. However, it does not explicitly contrast this tool with alternatives like memory_create_batch or memory_migrate_images, which could be confused with import functionality.

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