memory_export

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

The description mentions the return fields (version, memories, exportedAt) and implies a non-destructive snapshot operation, but it does not explicitly state that no state is modified. In the absence of annotations, this level of detail is somewhat lacking for full 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 extremely concise, containing only one sentence with no redundant information. It efficiently conveys the operation, purpose, and return structure.

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 low complexity (one optional parameter, no output schema), the description is sufficiently complete. It states the operation, its purpose, and the expected return fields, enabling an agent to use it correctly without further context.

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 single parameter actorId is fully described with its meaning and default behavior. Schema coverage is 100%, and the description adds complete semantic clarity beyond the schema.

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 exports a snapshot of memories for backup or migration, with a specific verb and resource. It distinguishes itself from sibling tools like memory_import and memory_get by focusing on exporting a full snapshot rather than individual retrieval or ingestion.

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?

It provides the intended use cases (backup or migration) and notes the optional actorId parameter with a default behavior. It does not explicitly mention when not to use it, but the purpose is sufficiently unambiguous.

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