Validate schema migrations within a StatelyDB elastic schema definition to ensure correctness before deployment.
Validate schema migrations inside of a StatelyDB elastic schema definition.
| Name | Required | Description | Default |
|---|---|---|---|
| schema | Yes | The schema definition to validate | |
| schemaId | Yes | The schema ID |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It doesn't disclose whether validation is read-only, what it returns, whether it fails fast, or what conditions cause failure — only that some validation happens.
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?
A single efficient sentence with the verb and scope front-loaded. No filler or 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?
For a validation tool with no annotations and no output schema, the description should explain what a successful or failed validation yields. Instead it stops at the purpose, leaving an agent without enough to interpret results.
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 both parameters are documented in the schema. The description adds no syntax or format detail beyond restating that the schema is validated, so the baseline of 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?
The description states a clear verb (validate) and resource (schema migrations inside a StatelyDB elastic schema definition), distinguishing it from the sibling statelydb-validate-schema via the 'migrations' scope. It does not explicitly name the sibling or explain the boundary, but the resource is specific enough.
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?
No when-to-use or when-not-to-use guidance is present. It does not say how it differs from statelydb-validate-schema or when a caller should prefer this tool, leaving the agent to infer from names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.