Here are some early testing results I'd like to share with anybody who wants to look at this.

Switching the strict mode to true pushes additional requirements on the schem:

• can't use minimum with integer type (makes sense from a JSON schema spec perspective)
• can't use uniqueItems on array types ???
• all query parameters need to be required ???

This last one is really problematic in a scenario where you have more parameters than there's context for.
E.g. with GET https://graph.microsoft.com/v1.0/me/messages with supports:

• includeHiddenMessages
• $search
• $top
• $skip
• $filter
• $select
• $expand
• $orderby

And the prompt using only the subject, recap my last 5 emails ordered by created date time, the model only has enough information for top/select/orderby, and might be able to figure out to set skip to 0. Gpt4 then gives up saying it couldn't call the function, and doesn't do a better job with the orderby parameter formatting, gpt4o defaults all others to the default for the type, which ends up failing on the service since the request doesn't make sense.

@SergeyMenshykh it looks like the work to normalize the schema is already started at #9807