generate_migration_plan

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that no files are written, implying the manifest is returned rather than persisted. However, it does not clarify whether the tool reads from application_path, whether there are other side effects, or what the generated manifest contains beyond being 'actionable'.

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 filler. It efficiently conveys the core purpose and the notable non-file-writing behavior.

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 5-parameter tool with no annotations, the one-sentence description is too thin. It leaves parameter semantics and sibling differentiation unresolved; the output schema exists, but the agent still cannot reliably determine when or how to call 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?

Schema description coverage is 0%, so the description must compensate, but it does not explain source, target, source_platform, target_platform, or application_path. The parameter names hint at a migration direction, but an agent cannot determine the expected value formats or relationships between source/target and source_platform/target_platform.

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 states a specific verb ('Generate'), a concrete deliverable ('actionable application-level migration manifest'), and a clear non-effect ('without writing files'). This distinguishes it from sibling report/session-plan tools even without naming them.

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 gives no explicit guidance on when to choose this tool over generate_migration_report, generate_session_migration_plan, or other migration-related siblings. The 'without writing files' phrase implies a read-only intent but does not state selection criteria or prerequisites.

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