analyze_liquibase

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

Given no annotations, the description reveals behavioral traits well: it details the analysis scope (lock risks, data loss, unsafe patterns) and specifies lock types (ACCESS EXCLUSIVE, SHARE). However, it does not explicitly state that the tool is read-only and has no side effects, which would be helpful.

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 concise and well-structured: it front-loads the primary purpose, lists supported change types in a bullet-like manner, and mentions output details. Every sentence adds value without redundancy.

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 description is fairly complete for a simple tool with one parameter and no output schema. It covers input, analysis scope, and types of returns (lock risk severity, data loss risk). However, it lacks detail on the output format or structure, which is necessary since there is no output schema.

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%, so the schema already describes the 'xml' parameter. The description reinforces that the input is a Liquibase XML changelog but adds no new semantic details beyond what the schema provides. Baseline score 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's purpose: 'Analyze a Liquibase XML changelog for lock risks, data loss potential, and unsafe patterns.' It lists supported change types and inline SQL analysis, making it specific and distinct from siblings like analyze_liquibase_yaml.

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?

Usage context is implied (use when analyzing Liquibase XML changelogs), but no explicit guidance on when not to use it or how to choose among siblings like analyze_migration or analyze_liquibase_yaml. This leaves ambiguity for an AI agent.

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