Import memories

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

Goes well beyond the annotations: validation-before-write, single-transaction atomicity ('a bad item changes nothing'), duplicate and expired-item skipping, field preservation and timestamp-to-UTC conversion, plus the exact return keys. This is exactly the behavioral detail annotations like idempotentHint and destructiveHint cannot convey.

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?

Front-loaded with the source relationship, then consequences, then return shape in three tight sentences. No filler; every clause carries actionable 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 one-parameter import tool with no output schema, the description supplies the return keys, the atomicity guarantee, and the dedup/expiry behavior. Combined with the annotations, an agent has everything needed to invoke and interpret it.

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?

Schema coverage is 100% but the schema itself is nearly opaque (an array of objects with additionalProperties). The description compensates by specifying the required non-empty 'content' field and which optional fields are preserved, adding real meaning beyond the schema. It could still clarify the accepted timestamp formats more concretely.

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+resource ('Import memories') and ties the input source directly to the sibling tool export_memories, so an agent can immediately distinguish this from remember/update_memory and knows where the payload originates.

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?

Explicitly frames the use case as restoring data from a prior export_memories call, which is clear context. It stops short of stating when-not to use it (e.g., for single ad-hoc additions, use remember instead), leaving that routing to inference.

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