generate_migration_report

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

With no annotations, the description carries the full burden of explaining behavior, but it only states that a report is generated. It does not disclose whether the tool reads files, runs analysis, requires prior outputs, has side effects, or how the report is delivered.

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 short, but it is under-specified rather than appropriately concise. It lacks the front-loaded scoping and parameter context needed to be useful for a tool with five parameters, three of which are required.

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 no annotations, 0% schema description coverage, and no parameter explanations, the description is incomplete for an agent attempting to invoke the tool correctly. The output schema provides some return-value context, but the input meaning and integration workflow context remain unexplained.

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 explain any of the five parameters, including required ones like application_path, source, and target. The description adds no value in helping an agent understand what each parameter means or how to fill it.

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 action ('Generate') and the resource ('a human-readable report'), so the high-level purpose is understandable. However, it does not distinguish this tool from siblings like generate_migration_plan or generate_session_migration_plan, and the modifier 'from the integrated migration workflow' is vague.

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 explicit guidance on when to use this tool versus the many sibling migration tools. The phrase 'from the integrated migration workflow' weakly implies it should be used after workflow integration, but no prerequisites, alternatives, or exclusions are mentioned.

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