It leaves a lot of interpretation to the model. For example it doesn't give any guidance on concept naming or disambiguation, which leaves all of that work to the JSON schema.
In my experience it's much more effective to reference key terms or ideas in the JSON schema and then explain those and their constraints in the system prompt.
This is one reason why people often think one model performs better than another for tasks they are both capable of. The real question IMO becomes, does porking all of that extra input prompt (a) eat too much context or (b) increase cost too much.
It leaves a lot of interpretation to the model. For example it doesn't give any guidance on concept naming or disambiguation, which leaves all of that work to the JSON schema.
In my experience it's much more effective to reference key terms or ideas in the JSON schema and then explain those and their constraints in the system prompt.
This is one reason why people often think one model performs better than another for tasks they are both capable of. The real question IMO becomes, does porking all of that extra input prompt (a) eat too much context or (b) increase cost too much.
We will put an update on this in the future and post it in our blog, https://blog.devrupt.io/