export_memories

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

Annotations indicate readOnlyHint=false and destructiveHint=false, meaning the tool is not read-only nor destructive. The description adds that it exports all memories as JSONL, which implies a safe, non-destructive read-like operation. However, it does not disclose potential performance impacts or database locking behavior, which would be useful for low-latency scenarios.

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 very concise: two sentences, no extraneous information. The first sentence states the core functionality, and the second provides usage guidance. Information is front-loaded and each sentence earns its place.

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 tool has 0 parameters, an output schema, and annotations, the description is complete. It explains the output format (JSONL), the scope (all memories), and the use case (backup or raw dump). No additional information is necessary for an agent to correctly invoke this tool.

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 parameters with 100% schema coverage, so the description does not need to explain parameters. Baseline for 0 parameters is 4, and the description adds no extra parameter info, which 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 exports all memories as JSONL, specifying the verb, resource, and output format. It distinguishes from siblings like import_memories and list_memories by explicitly calling it an export for backup or raw dump.

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 includes an 'ACTION GUIDE' that explicitly states when to use: when the user requests a backup or raw dump. It does not explicitly state when not to use, but the context is clear, and the sibling tools cover other operations.

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