Pending changesets (structured)

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

Annotations already declare readOnlyHint=true, so the safety profile is known; the description adds that output is structured JSON and that the result distinguishes up-to-date from pending. The PATH/mise note usefully warns the agent not to wrap the command, but nothing is said about exit behavior, failure modes, or DB connectivity requirements.

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 short sentences, with the core purpose front-loaded and the practical PATH note trailing. Nothing is padding, though the environment note is tangential to the core description and could have been folded in more tightly.

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?

An output schema exists, so return values need no explanation, and annotations cover the read-only safety profile while the schema fully documents parameters. The description covers purpose and output shape adequately; only connectivity/prerequisite context is missing.

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 all six optional parameters (cwd, labels, contexts, extraArgs, defaultsFile, changelogFile) are already documented in the schema. The description adds no filter syntax or precedence hints beyond that, so the baseline 3 applies.

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 plus scope: 'List Liquibase changesets not yet applied to the target database, as structured JSON.' That is clearly distinguishable from siblings like liquibase_update_sql or liquibase_validate, though no sibling is named explicitly.

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 intent (check pending changesets before applying) is implied by 'not yet applied' and 'Reports up-to-date vs a pending list', but there is no explicit when-to-use or when-not-to-use guidance versus liquibase_validate or liquibase_update_sql. The 'liquibase is on PATH' note is operational rather than tool-selection guidance.

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