generate_rollback

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

No annotations exist, so the description must fully disclose behavior. It mentions generating rollback SQL with warnings for irreversible operations and Flyway schema_history cleanup. However, it does not clarify execution side effects (e.g., does it apply changes or only produce text?) or authentication requirements, leaving some behavioral gaps.

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 extremely concise at two sentences, with no filler. It is front-loaded with the primary action ('Generate reverse DDL') and then adds key details, making it easy for an agent to parse quickly.

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?

Without an output schema, the description partially compensates by stating the tool produces rollback SQL with warnings and Flyway cleanup. However, it does not describe the format of the output or how warnings are presented, leaving some ambiguity for an agent expecting a structured response.

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?

The input schema has 100% coverage with descriptions for both 'filename' and 'sql'. The description adds no additional meaning beyond the schema examples (e.g., filename format is already illustrated). Thus, it meets the baseline for high schema coverage but does not compensate further.

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's purpose: 'Generate reverse DDL to undo a SQL migration.' It specifies the output (rollback SQL with warnings for irreversible operations) and mentions Flyway cleanup, distinguishing it from sibling analysis tools like analyze_migration and detect_conflicts.

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 implies usage when undoing a migration but does not explicitly state when to use this tool versus alternatives, nor does it provide 'when not to use' guidance. It lacks explicit comparison with sibling tools, leaving room for ambiguity.

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