{"version":"2.1.260","anchor":"structured-output-tool-now-lints-schemas-for-unsatisfiabilit","canonical_anchor":"structured-output-tool-now-lints-schemas-for-unsatisfiabilit","heading":"Structured-output tool now lints schemas for unsatisfiability","tier":"internal","area":"Structured Output","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/structured-output-tool-now-lints-schemas-for-unsatisfiabilit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Structured-output tool now lints schemas for unsatisfiability\n\nStructuredOutput schemas are now linted for internally-contradictory constraints.\n\nStructuredOutput tool schemas are now analyzed for internally-contradictory constraints, such as crossed min\/max bounds, required properties missing from `properties` with `additionalProperties: false`, and enum\/const type mismatches, in addition to the existing strict-schema conversion. Findings are surfaced via a new `unsatisfiable` field and reported through the `tengu_structured_output_schema_lint` telemetry event.\n\n- Area: Structured Output\n- Names: `tengu_structured_output_schema_lint`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}