generate_migration

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it generates scripts but does not explain side effects, return format, whether changes are applied, or any execution requirements. This is a significant gap for a tool that likely produces files or output.

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, concise sentence without redundant words. However, it is so brief that it omits crucial details about usage, output, and constraints, making it under-specified rather than appropriately sized. Conciseness without informativeness warrants a mid score.

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 the nested structure of the changes parameter and the absence of an output schema, the description is incomplete. It does not explain how changes should be structured beyond the schema, what the generated script contains, or any limitations. An agent would lack essential context to correctly use this tool.

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 100%, so both parameters have descriptions in the schema. The tool description adds no parameter-specific context beyond the schema, which already explains migrationName naming and changes as an array of changes. Baseline 3 is appropriate.

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 the tool generates database migration scripts for schema changes, with a specific verb and resource. It does not differentiate from sibling generate_plugin_migration, but the scope is clear enough for basic selection.

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?

No guidance is provided on when to use this tool versus alternatives like generate_plugin_migration. The description offers no context about scenarios, prerequisites, or conditions that would favor this tool over its siblings.

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