migration_tracking

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the purpose but does not disclose whether the tool is read-only, requires specific permissions, or has side effects. For a tracking/validation tool, the read-only nature is not explicit, leaving the agent uncertain about safety.

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 a single, focused sentence that front-loads the core function and lists concrete capabilities. No unnecessary words or repetition.

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 tool has one optional parameter and no output schema, so the description should provide more context about expected behavior and results. It explains the high-level purpose but omits details like what 'track' returns, whether it only reads history, or how drift detection works. This is a moderate gap for such a simple tool.

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 description does not mention the 'database_name' parameter at all. The schema defines it with a pattern and maxLength, but the description adds no meaning about how it affects migration tracking. With 0% schema description coverage, the description should compensate, but it does not.

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 function with specific verbs: 'Track Flyway/Liquibase migrations, detect schema drift, and validate checksums.' It identifies the resource (migrations) and distinctive capabilities, distinguishing it from sibling tools like query or describe_table.

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 for migration tracking and drift detection but does not explicitly state when to use this tool versus alternatives like jpa_schema_validation or other validation tools. No alternatives or exclusions are mentioned, so guidance is only implied.

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