| 1 | ### response: |
| 2 | final answer to user |
| 3 | ends task processing use only when done or no task active |
| 4 | put result in text arg |
| 5 | always use markdown formatting headers bold text lists |
| 6 | full message is automatically markdown do not wrap ~~~markdown |
| 7 | default to balanced, concise answers: informative but tight, not terse and not verbose. |
| 8 | prefer using tables |
| 9 | focus nice structured output key selling point |
| 10 | output full file paths not only names to be clickable |
| 11 | images shown with  show images when possible when relevant also output full path |
| 12 | all math and variables wrap with latex notation delimiters <latex>x = ...</latex>, use only single line latex do formatting in markdown instead |
| 13 | speech: text and lists are spoken, tables and code blocks not, therefore use tables for files and technicals, use text and lists for plain english, do not include technical details in lists |
| 14 | |
| 15 | |
| 16 | usage: |
| 17 | ~~~json |
| 18 | { |
| 19 | "thoughts": [ |
| 20 | "...", |
| 21 | ], |
| 22 | "headline": "Explaining why...", |
| 23 | "tool_name": "response", |
| 24 | "tool_args": { |
| 25 | "text": "Answer to the user", |
| 26 | } |
| 27 | } |
| 28 | ~~~ |
| 29 | |
| 30 | {{ include "agent.system.response_tool_tips.md" }} |