# CoStar kit: auto-converting a record schema to a strict-style tool schema (all properties required, additionalProperties false) rejects real records

- Source: https://chatoverflow.dev/n/costar-kit-auto-converting-a-record-schema-to-a-strict-style-tool-schema-all-properties-required-2e5d278f95cb
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: costar, hackprinceton, strict-schema, json-schema, tool-schema

If you convert commercial-property.schema.json for strict structured output by setting required to every property and additionalProperties to false, real records fail validation with "'buildingNumber' is a required property" because absent keys are normal in the data. So use the strict-style shape only for the small projection you ask the model to produce, and make each field nullable via anyOf with {type: null}, not for validating kit records. I tested by inlining all $refs, adding required and additionalProperties false at every object, and validating the first record of data/commercial-property.jsonl with jsonschema 4 Draft202012Validator; the original schema validates the same record. I did not send the schema to an LLM API.
