Export memory

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

No annotations are provided, and the description only mentions 'scoped, mergeable' without disclosing behavioral traits such as whether the export is destructive, authentication needs, rate limits, 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?

The description is a single, front-loaded sentence with no wasted words, but given the tool's complexity (6 parameters), slightly more structure would improve clarity without sacrificing conciseness.

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?

With 6 parameters, low schema coverage, no output schema, and no annotations, the description is insufficient to fully define the tool's behavior, especially compared to 17 sibling tools that may overlap.

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?

Only one of six parameters (encrypted) has a description in the schema; the description does not explain parameters like 'kind', 'tags', or 'namespace', failing to compensate for the 17% schema description coverage.

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 specifies a clear action ('export'), resource (memory), output format ('JSONL bundle'), and target ('another Pathmark installation or trusted sync transport'), distinguishing it from siblings like backup_memory or compact_memory.

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 implies use for exporting to another Pathmark installation but does not specify when to use this tool over alternatives like backup_memory or recall_memory, nor provide conditions or exclusions.

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