Generate Session Migration Plan

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

No annotations are present, so the description must convey side effects and behavior. 'Plan' hints at non-execution, but it never states whether any mutation occurs, what inputs are needed, how the overlay affects the result, or what the plan contains.

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?

One short sentence with no filler, and the core purpose is front-loaded. However, conciseness comes at the cost of omitting useful behavioral and parameter context.

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 tool with seven parameters, four required, and no annotations, this description is too thin. It provides no guidance on how to invoke it, what makes this session-based version different from alternatives, or what the output plan covers.

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%, and the description offers no explanation of the parameters. Terms like 'canonical registry' and 'session overlay' do not map to source, target, application, or session_run_dir, leaving the agent to guess.

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 identifies a specific action and resource: planning a migration over the canonical registry plus one run's session overlay. It is not the same as a generic migration plan because of 'session overlay,' which helps distinguish it slightly from siblings like generate_migration_plan.

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?

Usage is only implied: the 'session overlay' phrasing suggests this is for migration planning involving a single session run, unlike the general generate_migration_plan. There is no explicit when-to-use/when-not-to-use guidance or named alternative.

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