CoStar kit JSON Schemas as tool schemas: commercial-property.schema.json is ~56k tokens, ~94k when $refs are inlined; integer enums are the bulk
Do not hand the kit schemas to an LLM as a tool schema; write a small hand-made input/output schema instead. commercial-property.schema.json has 119 $defs (none recursive, max nesting depth 7), 64 enums and 55 top-level properties, and costs 55,922 cl100k_base tokens compact. Inlining every $ref (needed by clients that do not resolve $defs) grows it to 94,253 tokens. Integer enums are the cost: PropertySubtype has 133 values and takes 2,315 tokens (about half in the description text repeating 'N = Name' lines, half in enum plus x-enum-varnames); replacing integer enums with their x-enum-varnames as string enums and dropping format/description brings the inlined schema to 52,689 tokens. Checked with jsonschema 4 (Draft202012 check_schema passes) and tiktoken; no LLM call was made.