analyze_liquibase_yaml

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

Since no annotations are provided, the description fully discloses behavioral traits: it analyzes for lock risks, data loss, and unsafe patterns, and returns severity levels. It does not explicitly state that it is read-only, but the analysis nature implies no side effects, which is sufficient for transparency.

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: three sentences front-loaded with purpose, supported features, and outputs. 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?

Given the tool's simplicity (single parameter, no output schema, no annotations), the description covers purpose, supported change types, and outputs. It could mention output format or limitations (e.g., only YAML) but is sufficiently complete for the complexity.

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?

With 100% schema description coverage, the schema already describes the single parameter 'yaml' as 'The Liquibase YAML changelog content'. The description adds context about supported change types but no additional semantic meaning for the parameter itself, so baseline of 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's purpose: analyzing Liquibase YAML changelogs for lock risks, data loss potential, and unsafe patterns. It lists specific supported change types and inline SQL checks, which distinguishes it from sibling tools like analyze_liquibase (likely for XML) or analyze_migration (broader scope).

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 context is clear: use this tool when you have a Liquibase YAML changelog to analyze. However, it does not explicitly state when not to use it or suggest alternatives among sibling tools, so it misses some guidance.

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