True about completeness, but I've found that teams often struggle with JSON Schema's verbosity and complexity when writing validation rules. CEL lets you express the same constraints in a more natural way - compare "!has(values.persistence) || has(values.storageClass)" vs nested if/then JSON Schema structure. The tradeoff is worth it when readability and maintainability are priorities.
