Asked about Designing schemas the model fills well

Why does field order in a schema matter?

An answer that works

The model generates the output in order. If the conclusion comes first it is chosen before any supporting text is written. Putting evidence or reasoning fields before the conclusion lets the conclusion depend on them.

Then they push further

Does that mean you should always add a reasoning field?

No. It costs output tokens on every call and is only worth it where the decision is hard. Measure accuracy with and without it on your eval. For simple fields it adds cost and nothing else.

What gets marked up

Marked up for linking it to left-to-right generation and for treating the reasoning field as a cost to be measured, not a free win.

Reading an answer is not being able to give one. The section that teaches this is Designing schemas the model fills well, 4 hours of Structured output.

Learn this properly

Also asked about Structured output

Your extraction pipeline returns malformed JSON 5 percent of the time. What are the likely causes?What does a response schema guarantee?How does constrained decoding actually work?Should every field be required?How would you reduce invented values in an extraction pipeline?Your classification enum has an 'other' option that is now used 30% of the time. What does that tell you?How would you measure the accuracy of an invoice extraction pipeline?When would you use a batch API?

All 10 questions on Structured output