memento_migrate_workspace_memories

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

With no annotations provided, the description must disclose behavioral traits. It states 'copy-only migration' indicating non-destructive behavior, but fails to explain side effects, idempotency, error handling, or safety considerations like whether the source DB is modified or if the tool can be re-run safely.

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 concise with a single sentence and a result note. It front-loads the key action and output, avoiding unnecessary verbosity. However, it could benefit from structured sections for clarity.

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 migration tool with no output schema and limited schema descriptions, the description omits important context such as the format of the JSON report, expected behavior under failure, required permissions, and the exact nature of the 'deterministic text heuristics'. This leaves significant gaps for an agent.

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 25% of schema parameters have descriptions (workspace_root has a description but contradictory 'MANDATORY' vs not required in schema). The tool description does not compensate for the missing parameter explanations for source_db_path, workspace_roots, and report_path, leaving agents uncertain about input requirements.

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 it is a 'copy-only migration' tool that redistributes memories from a source DB into per-workspace DBs using deterministic text heuristics, which distinguishes it from other memento tools that handle queries or configurations. However, it could explicitly contrast with sibling tools like memento_remember or memento_search.

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 does not provide explicit guidance on when to use this tool versus alternatives. It implies usage when migration is needed, but lacks conditions, prerequisites, or when not to use it. No mention of alternatives among siblings.

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