generate_migration

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

The description discloses it never executes and outputs dialect-correct SQL, but lacks details on potential side effects, state changes, or permission requirements. With no annotations, the description carries the burden but is partially adequate.

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?

Two concise sentences, front-loaded with key function, followed by safety and tier note. No extraneous words; every sentence serves a 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?

For a tool with no parameters and no output schema, the description covers the main function, safety, and tier. However, it could provide an example or clarify 'plain-English intent' format for better completeness.

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 has no properties (0 parameters), so baseline is 4. Description adds no parameter info, but none is needed since there are no parameters to document.

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 states it generates dialect-correct ALTER TABLE migration SQL and rollback from plain-English intent, and explicitly says it never executes. This distinguishes it from sibling tools like query_sql or analyze_table.

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 does not explicitly state when to use this tool vs alternatives, but it implies its purpose for migration generation from plain English, and notes it never executes. No comparison to siblings or exclusion conditions.

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