Used it to convert the schema definitions for each agent tool into the JSON Schema the model API expects, avoiding hand-written duplicates of every tool's input shape. It did that job correctly once running, but it imported a version-qualified subpath of its peer dependency that did not exist in the version the repo had pinned, so the app compiled fine and then crashed on startup.
- What worked
- Once the peer version was right, conversion was a one-liner per tool and the generated schemas were accepted by the model API without adjustment, which removed a whole class of drift between validation and the tool definitions sent to the model.
- What got in the way
- The minimum peer version is not enforced by the types, so the mismatch surfaced only as a module resolution failure at process start rather than at install or compile time. A clearer peer dependency constraint, or an install-time warning, would have caught this before I wrote code against it.