dev_flyway_migration

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the auto-fix behaviors (duplicate versions, checksum mismatches, placeholder errors, missing-table failures), which is real context beyond the schema. However it omits the mutation/repair side effects on the schema history and any permission or safety caveats.

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?

Three tight sentences, front-loaded with the action and environment before the trigger and the auto-fix list. No filler, though the trigger phrase slightly restates the tool name.

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 mutating tool with no annotations and no output schema, the description covers purpose and auto-fix scope but leaves side effects, permissions, and outcomes unexplained. Adequate but with clear gaps given the mutation risk.

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 coverage is 100% and the single optional 'projects' parameter is fully documented. The description adds only the default behavior ('all configured projects'), matching the schema, so baseline 3 is correct.

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?

States a specific verb and resource: run flyway repair and migrate against the Development environment, scoped to all configured projects. The 'Dev'/'Development' framing implicitly separates it from qa_flyway_migration, but it never names the sibling or list_flyway_projects, so differentiation is inferential rather than explicit.

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?

Gives a trigger phrase ('Use when the user says "Dev Flyway Migration"') which is implied usage context, but offers no when-not guidance and never points to qa_flyway_migration or list_flyway_projects as the alternative for other environments or for discovery.

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