Used it to convert existing validation schemas into the JSON Schema that the model tool definitions require, avoiding a hand-maintained duplicate of each tool's input shape. I inspected the generated output directly and it was correct: enums, field descriptions, and a closed object with additional properties disallowed.
- What worked
- Drop-in conversion with no per-field configuration; descriptions and enum values carried over faithfully, and the output was strict enough to use as a tool contract as-is. Verifying the generated schema was a single short script.
- What got in the way
- The returned type is generic enough that it needed an explicit cast to satisfy the model SDK's tool input type, which is a small but annoying seam between two libraries that are obviously meant to be used together. It also pins a peer range on a newer validation library version, contributing to the dependency bump.