Fix tool call description

README.md

@@ -108,7 +108,7 @@ The multi-turn template is the same with non-thinking multi-turn chat template.
 ### ToolCall
 Toolcall is supported in non-thinking mode. The format is: 
 
-`<｜begin▁of▁sentence｜>{system prompt}{tool_description}<｜User｜>{query}<｜Assistant｜></think>` where the tool_description is 
+`<｜begin▁of▁sentence｜>{system prompt}\n\n{tool_description}<｜User｜>{query}<｜Assistant｜></think>` where the tool_description is 
 
 ```
 ## Tools
@@ -120,7 +120,7 @@ Description: {description}
 Parameters: {json.dumps(parameters)}
 
 IMPORTANT: ALWAYS adhere to this exact format for tool use:
-<｜tool▁calls▁begin｜><｜tool▁call▁begin｜>tool_call_name<｜tool▁sep｜>tool_call_arguments<｜tool▁call▁end｜>{{additional_tool_calls}}<｜tool▁calls▁end｜>
+<｜tool▁calls▁begin｜><｜tool▁call▁begin｜>tool_call_name<｜tool▁sep｜>tool_call_arguments<｜tool▁call▁end｜>{additional_tool_calls}<｜tool▁calls▁end｜>
 
 Where:
 - `tool_call_name` must be an exact match to one of the available tools

assets/code_agent_trajectory.html

@@ -8,7 +8,44 @@
   .red    { background:#FFCDD2;    }
   .blue   { background:#BBDEFB;   }
 </style>
-<div>You are a helpful software engineer assistant.<span class="token yellow">&lt;｜User｜&gt;</span>&lt;uploaded_files&gt;
+<div>You are a helpful software engineer assistant.
+
+## Tools
+You have access to the following tools:
+
+### bash
+Description: Run commands in a bash shell
+* When invoking this tool, the contents of the &quot;command&quot; parameter does NOT need to be XML-escaped.
+* You don&#x27;t have access to the internet via this tool.
+* You do have access to a mirror of common linux and python packages via apt and pip.
+* State is persistent across command calls and discussions with the user.
+* To inspect a particular line range of a file, e.g. lines 10-25, try &#x27;sed -n 10,25p /path/to/the/file&#x27;.
+* Please avoid commands that may produce a very large amount of output.
+* Please run long lived commands in the background, e.g. &#x27;sleep 10 &amp;&#x27; or start a server in the background.
+
+Parameters: {&quot;title&quot;: &quot;BashInput&quot;, &quot;type&quot;: &quot;object&quot;, &quot;properties&quot;: {&quot;command&quot;: {&quot;title&quot;: &quot;Command&quot;, &quot;description&quot;: &quot;The bash command to run. Relative path is preferred in the command.&quot;, &quot;type&quot;: &quot;string&quot;}}, &quot;required&quot;: [&quot;command&quot;], &quot;additionalProperties&quot;: false}
+
+### str_replace_editor
+Description: Custom editing tool for viewing, creating and editing files
+* State is persistent across command calls and discussions with the user
+* If `path` is a file, `view` displays the result of applying `cat -n`. If `path` is a directory, `view` lists non-hidden files and directories up to 2 levels deep
+* The `create` command cannot be used if the specified `path` already exists as a file
+* If a `command` generates a long output, it will be truncated and marked with `&lt;response clipped&gt;`
+
+Notes for using the `str_replace` command:
+* The `old_str` parameter should match EXACTLY one or more consecutive lines from the original file. Be mindful of whitespaces!
+* If the `old_str` parameter is not unique in the file, the replacement will not be performed. Make sure to include enough context in `old_str` to make it unique
+* The `new_str` parameter should contain the edited lines that should replace the `old_str`
+
+Parameters: {&quot;title&quot;: &quot;SweEditorInput&quot;, &quot;type&quot;: &quot;object&quot;, &quot;properties&quot;: {&quot;command&quot;: {&quot;title&quot;: &quot;Command&quot;, &quot;description&quot;: &quot;The commands to run. Allowed options are: `view`, `create`, `str_replace`, `insert`.&quot;, &quot;enum&quot;: [&quot;view&quot;, &quot;create&quot;, &quot;str_replace&quot;, &quot;insert&quot;], &quot;type&quot;: &quot;string&quot;}, &quot;path&quot;: {&quot;title&quot;: &quot;Path&quot;, &quot;description&quot;: &quot;Absolute path to file or directory, e.g. `/repo/file.py` or `/repo`.&quot;, &quot;type&quot;: &quot;string&quot;}, &quot;file_text&quot;: {&quot;title&quot;: &quot;File Text&quot;, &quot;description&quot;: &quot;Required parameter of `create` command, with the content of the file to be created.&quot;, &quot;type&quot;: &quot;string&quot;}, &quot;insert_line&quot;: {&quot;title&quot;: &quot;Insert Line&quot;, &quot;description&quot;: &quot;Required parameter of `insert` command. The `new_str` will be inserted AFTER the line `insert_line` of `path`.&quot;, &quot;type&quot;: &quot;integer&quot;}, &quot;new_str&quot;: {&quot;title&quot;: &quot;New Str&quot;, &quot;description&quot;: &quot;Optional parameter of `str_replace` command containing the new string (if not given, no string will be added). Required parameter of `insert` command containing the string to insert.&quot;, &quot;type&quot;: &quot;string&quot;}, &quot;old_str&quot;: {&quot;title&quot;: &quot;Old Str&quot;, &quot;description&quot;: &quot;Required parameter of `str_replace` command containing the string in `path` to replace.&quot;, &quot;type&quot;: &quot;string&quot;}, &quot;view_range&quot;: {&quot;title&quot;: &quot;View Range&quot;, &quot;description&quot;: &quot;Optional parameter of `view` command when `path` points to a file. If none is given, the full file is shown. If provided, the file will be shown in the indicated line number range, e.g. [11, 12] will show lines 11 and 12. Indexing at 1 to start. Setting `[start_line, -1]` shows all lines from `start_line` to the end of the file.&quot;, &quot;type&quot;: &quot;array&quot;, &quot;items&quot;: {&quot;type&quot;: &quot;integer&quot;}}}, &quot;required&quot;: [&quot;command&quot;, &quot;path&quot;], &quot;additionalProperties&quot;: false}
+
+IMPORTANT: ALWAYS adhere to this exact format for tool use:
+<span class="token green">&lt;｜tool▁calls▁begin｜&gt;</span><span class="token green">&lt;｜tool▁call▁begin｜&gt;</span>tool_call_name<span class="token green">&lt;｜tool▁sep｜&gt;</span>tool_call_arguments<span class="token green">&lt;｜tool▁call▁end｜&gt;</span>{additional_tool_calls}<span class="token green">&lt;｜tool▁calls▁end｜&gt;</span>
+
+Where:
+- `tool_call_name` must be an exact match to one of the available tools
+- `tool_call_arguments` must be valid JSON that strictly follows the tool&#x27;s Parameters Schema
+- For multiple tool calls, chain them directly without separators or spaces<span class="token yellow">&lt;｜User｜&gt;</span>&lt;uploaded_files&gt;
 /testbed
 &lt;/uploaded_files&gt;
 I&#x27;ve uploaded a code repository in the directory /testbed (not in /tmp/inputs). Consider the following PR description: