memory_migration

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

No annotations are present, so the description must fully convey behavioral traits. It only states the high-level action without disclosing side effects, destructive potential, or execution details. The tool performs three distinct actions (create_plan, execute_migration, validate_compatibility) but the description lumps them together without distinction.

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 sentence, making it concise. However, it lacks structure; it does not separate the three distinct actions or provide a hierarchical breakdown. While front-loaded with the main verb, crucial details are omitted, making it less effective than a more structured brief.

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's complexity (three actions, nested objects, no output schema), the description is insufficient. It does not explain the workflow, expected inputs for each action, or return values. An agent would need to infer behavior from the action enum alone, which is risky.

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?

Of 6 parameters, only sourceSchema and targetSchema have descriptions in the schema (50% coverage). The description adds no new information about parameters, such as what 'action' values mean or how 'migrationPlan' is structured. It fails to compensate for the schema's lack of descriptions.

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 identifies the tool's purpose: creating and executing migration plans between memory systems. The verb 'Create and execute' and resource 'migration plans' are specific, and the context 'between different memory systems' adds clarity. However, it does not explicitly distinguish from sibling tools like memory_export or memory_import_advanced, which may involve data movement.

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?

No usage guidelines are provided. The description does not indicate when to use this tool over alternatives (e.g., memory_export for one-time transfers). There is no mention of prerequisites, typical scenarios, or prohibitions.

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