This is a little tricky. At this point, we allow things like ["param" "foo"] as field, where "foo" can't be validated. This isn't an issue in the "expanded form", but error messages for expanded form queries probably won't make much sense to users as it won't be what they typed in. I'm side stepping this for now. The error messages should still be better for non-nested query clauses