Export memory contents (requires explicit_user_intent)

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

Annotations indicate readOnlyHint=true and idempotentHint=true, and the description aligns by calling it a dump (read operation) and requiring explicit user intent. It adds the behavioral trait that explicit_user_intent must be set only when user explicitly asks.

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 two sentences, front-loading the core purpose. Every sentence adds value: first sentence states action and formats, second adds optional filtering and use case.

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 no output schema, the description covers output formats and use case (backup/inspection). With 4 parameters fully described in schema and the description adding optional window context, it is sufficient for the tool's complexity.

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%, so baseline is 3. The description mentions 'Optional since/until window on updated_at' which adds context beyond schema descriptions but does not significantly enhance semantic understanding beyond what schema already provides.

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 dumps memory store as JSON, JSONL, or Markdown, specifying the verb (dump/export) and resource (memory store) with output formats. It distinguishes from siblings by focusing on bulk export with format options.

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 says 'Use for backup/inspection', providing clear context. It also mentions the optional time window and requires explicit_user_intent. However, it does not explicitly state when not to use it or compare to alternatives among siblings.

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