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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds some behavioral context by naming the phased gates and AWS Transform integration discovery, but it does not clarify that this is advisory planning rather than execution or explain input requirements.

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 compact sentence with no wasted words, but that concision comes at the cost of under-specification. It is not front-loaded with the essential purpose or parameter context an agent needs.

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?

The tool has four required parameters with no schema descriptions, yet the description provides no parameter explanations or usage guidance. An output schema exists, so return values need not be described, but the input side and tool selection guidance are materially incomplete.

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 does not mention source, target, strategy, or constraints at all. With four required parameters and no parameter-level documentation in either the schema or the description, an agent receives no semantic guidance for invocation.

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 names a verb ('Prepare') and lists migration phases/gates (discovery, pilot, migration, rollback), which gives a rough idea of purpose. However, it never explicitly says it produces a migration plan, and it gives no differentiation from siblings like implementation_plan or architecture_pattern.

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?

There is no guidance on when to use this tool, when not to use it, or which sibling tools are alternatives. The agent must infer usage entirely from the name and sparse description.

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