|
154 | 154 | "Do NOT promise to call a function later. If a function call is required, emit it now; otherwise respond normally.\n",
|
155 | 155 | "```\n",
|
156 | 156 | "\n",
|
157 |
| - "2. Catch bad arguments early: \n", |
158 |
| - "Setting `strict` to `true` will ensure function calls reliably adhere to the [function schema](https://platform.openai.com/docs/guides/function-calling?api-mode=responses#strict-mode). We recommend turning it on whenever possible.\n", |
| 157 | + "2. Catch bad arguments early:\n", |
| 158 | + "setting `strict` to `true` will ensure function calls reliably adhere to the [function schema](https://platform.openai.com/docs/guides/function-calling?api-mode=responses#strict-mode). We recommend turning it on whenever possible.\n", |
159 | 159 | "\n",
|
160 | 160 | "If your arguments have additional complex format requirements (e.g valid python code etc), adding the following instruction can remind the model of the expected format. \n",
|
161 | 161 | "\n",
|
162 | 162 | "```\n",
|
163 | 163 | "Validate arguments against the format before sending the call; if you are unsure, ask for clarification instead of guessing.\n",
|
164 | 164 | "```\n",
|
165 | 165 | "\n",
|
166 |
| - "3. Another note on lazy behavior: \n", |
167 |
| - "We are aware of rare instances of lazy behavior from o3, such as stating it does not have enough time to complete a task, promising to follow up separately, or giving terse answers even when explicitly prompted to provide more detail. We have found that the following steps help ameliorate this behavior:\n", |
| 166 | + "3. Another note on lazy behavior:\n", |
| 167 | + "we are aware of rare instances of lazy behavior from o3, such as stating it does not have enough time to complete a task, promising to follow up separately, or giving terse answers even when explicitly prompted to provide more detail. We have found that the following steps help ameliorate this behavior:\n", |
168 | 168 | "\n",
|
169 | 169 | " a. Start a new conversation for unrelated topics:\n",
|
170 | 170 | " When switching to a new or unrelated topic, begin a fresh conversation thread rather than continuing in the same context. This helps the model focus on the current subject and prevents it from being influenced by previous, irrelevant context, which can sometimes lead to incomplete or lazy responses. For example, if you were previously discussing code debugging and now want to ask about documentation best practices, which does not require previous conversation context, start a new conversation to ensure clarity and focus.\n",
|
|
0 commit comments