fix: streamline ask_followup_question schema documentation for clarity and conciseness

Author: NaccOll

src/core/prompts/tools/schemas/ask-followup-question-schema.ts

@@ -4,68 +4,45 @@ import { BaseToolSchema } from "./base-tool-schema"
 export function generateAskFollowupQuestionSchema(args: ToolArgs): BaseToolSchema {
 	const schema: BaseToolSchema = {
 		name: "ask_followup_question",
-		description: `Ask the user a question to gather additional information needed to complete the task. This tool should be used when you encounter ambiguities, need clarification, or require more details to proceed effectively. It allows for interactive problem-solving by enabling direct communication with the user. Use this tool judiciously to maintain a balance between gathering necessary information and avoiding excessive back-and-forth.`,
+		description: `Ask the user a question to gather additional information needed to complete the task. Use when you need clarification or more details to proceed effectively.`,
 		parameters: [
 			{
 				name: "question",
 				type: "string",
-				description:
-					"The question to ask the user. This should be a clear, specific question that addresses the information you need.",
+				description: "A clear, specific question addressing the information needed",
 				required: true,
 			},
 			{
 				name: "follow_up",
 				type: "string",
-				description: `A list of 2-4 suggested answers that logically follow from the question, ordered by priority or logical sequence. Each suggestion must:
-1. Be provided in its own <suggest> tag
-2. Be specific, actionable, and directly related to the completed task
-3. Be a complete answer to the question - the user should not need to provide additional information or fill in any missing details. DO NOT include placeholders with brackets or parentheses.
-4. Optionally include a mode attribute to switch to a specific mode when the suggestion is selected: <suggest mode="mode-slug">suggestion text</suggest>
-   - When using the mode attribute, focus the suggestion text on the action to be taken rather than mentioning the mode switch, as the mode change is handled automatically and indicated by a visual badge`,
+				description: `A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.), such as '<suggest mode="mode-slug">suggestion text</suggest>'`,
 				required: true,
 			},
 		],
 		systemPropmt: `## ask_followup_question
-Description: Ask the user a question to gather additional information needed to complete the task. This tool should be used when you encounter ambiguities, need clarification, or require more details to proceed effectively. It allows for interactive problem-solving by enabling direct communication with the user. Use this tool judiciously to maintain a balance between gathering necessary information and avoiding excessive back-and-forth.
+Description: Ask the user a question to gather additional information needed to complete the task. Use when you need clarification or more details to proceed effectively.
+
 Parameters:
-- question: (required) The question to ask the user. This should be a clear, specific question that addresses the information you need.
-- follow_up: (required) A list of 2-4 suggested answers that logically follow from the question, ordered by priority or logical sequence. Each suggestion must:
-  1. Be provided in its own <suggest> tag
-  2. Be specific, actionable, and directly related to the completed task
-  3. Be a complete answer to the question - the user should not need to provide additional information or fill in any missing details. DO NOT include placeholders with brackets or parentheses.
-  4. Optionally include a mode attribute to switch to a specific mode when the suggestion is selected: <suggest mode="mode-slug">suggestion text</suggest>
-     - When using the mode attribute, focus the suggestion text on the action to be taken rather than mentioning the mode switch, as the mode change is handled automatically and indicated by a visual badge
+- question: (required) A clear, specific question addressing the information needed
+- follow_up: (required) A list of 2-4 suggested answers, each in its own <suggest> tag. Suggestions must be complete, actionable answers without placeholders. Optionally include mode attribute to switch modes (code/architect/etc.)
+
 Usage:
 <ask_followup_question>
 <question>Your question here</question>
 <follow_up>
-<suggest>
-Your suggested answer here
-</suggest>
-<suggest mode="code">
-Implement the solution
-</suggest>
+<suggest>First suggestion</suggest>
+<suggest mode="code">Action with mode switch</suggest>
 </follow_up>
 </ask_followup_question>
 
-Example: Requesting to ask the user for the path to the frontend-config.json file
+Example:
 <ask_followup_question>
 <question>What is the path to the frontend-config.json file?</question>
 <follow_up>
 <suggest>./src/frontend-config.json</suggest>
 <suggest>./config/frontend-config.json</suggest>
 <suggest>./frontend-config.json</suggest>
 </follow_up>
-</ask_followup_question>
-
-Example: Asking a question with mode switching options
-<ask_followup_question>
-<question>How would you like to proceed with this task?</question>
-<follow_up>
-<suggest mode="code">Start implementing the solution</suggest>
-<suggest mode="architect">Plan the architecture first</suggest>
-<suggest>Continue with more details</suggest>
-</follow_up>
 </ask_followup_question>`,
 	}
 	return schema