Skip to content

Commit 6332bb0

Browse files
committed
formatting
1 parent 33e9575 commit 6332bb0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

examples/o-series/o3o4-mini_prompting_guide.ipynb

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -366,9 +366,9 @@
366366
"**A:** Not guaranteed. The guidance in this document assumes you’re using the standard `tools` model parameter to pass your function schemas, as shown in our [general guide](https://platform.openai.com/docs/guides/function-calling) on function calling. Our o3/o4-mini models are trained to understand and use these schemas natively for tool selection and argument construction.\n",
367367
"\n",
368368
"If you’re instead providing custom tool definitions via natural language in a developer-authored prompt (e.g., defining tools inline in the developer message or user message), this guidance may not fully apply. In those cases:\n",
369-
"The model is not relying on its internal tool-schema priors\n",
370-
"You may need to be more explicit with few-shot examples, output formats, and tool selection criteria\n",
371-
"Argument construction reliability may degrade without schema-level anchoring\n",
369+
"The model is not relying on its internal tool-schema priors. \n",
370+
"You may need to be more explicit with few-shot examples, output formats, and tool selection criteria. \n",
371+
"Argument construction reliability may degrade without schema-level anchoring.\n",
372372
"\n",
373373
"Use the structured tools parameter when possible. If you must define tools in free text, treat it as a custom protocol and test accordingly.\n"
374374
]

0 commit comments

Comments
 (0)