generate_migration_script

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that it generates a script (not executes it) and includes the T-SQL language, which is useful context. However, it does not disclose details such as how schema_filter affects behavior or whether the script is returned as text. It does not contradict annotations, and the added value is modest.

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, tightly worded sentence that conveys the core functionality in under 15 words. There is no redundant phrasing or filler. Every word contributes to the purpose.

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 is relatively simple (3 parameters, one optional) and has an output schema. However, the description does not clarify what kind of output to expect (e.g., a script string, file path) or how the optional schema_filter narrows the generated script. While not critical, this missing context prevents a higher score.

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?

Input schema coverage is 100%, with each parameter having a basic description. The tool description adds no extra meaning beyond the schema; it only reiterates the overall transformation goal. This matches the baseline of 3 where the schema carries the parameter documentation weight.

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 uses a specific action verb ('Generate') with a concrete resource ('T-SQL migration script') and a clear goal ('transform source schema to match target'). This unambiguously distinguishes it from sibling tools like compare_schemas, which only compares schemas without generating scripts.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., need to run compare_schemas first) or situations where it should be avoided. The intended usage is only implied by the name and generic purpose, not stated.

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