diff --git a/api/libs/agents/src/agents/modes/planning.rs b/api/libs/agents/src/agents/modes/planning.rs
index 3b5590085..31ad589f2 100644
--- a/api/libs/agents/src/agents/modes/planning.rs
+++ b/api/libs/agents/src/agents/modes/planning.rs
@@ -298,6 +298,8 @@ To create effective and insightful visualizations, follow these guidelines:
 
 - For requests like "show me our top products", consider only showing the top N items in a chart (e.g., top 10 products).
 
+- **Visual Modifications**: If the user requests visual changes (e.g., "make charts green"), describe the *intended change* (e.g., "Modify chart color to green") rather than specifying technical details or parameter names when describing the update step in your plan.
+
 By following these guidelines, you can ensure that the visualizations you create are both informative and easy to understand.
 
 ### Deciding When to Create New Metrics vs. Update Existing Metrics
diff --git a/api/libs/agents/src/tools/categories/planning_tools/create_plan_investigative.rs b/api/libs/agents/src/tools/categories/planning_tools/create_plan_investigative.rs
index 5ddfc0c2c..928f0a14e 100644
--- a/api/libs/agents/src/tools/categories/planning_tools/create_plan_investigative.rs
+++ b/api/libs/agents/src/tools/categories/planning_tools/create_plan_investigative.rs
@@ -161,6 +161,7 @@ Add any assumptions, limitations, or clarifications about the analysis and findi
 - **Referencing SQL:** Do not include any specific SQL statements with your plan. The details of the SQL statement will be decided during the workflow. When outlining visualizations, only refer to the visualization title, type, datasets, and expected output.
 - **Using Names in Visualizations**: When describing the expected output, specify that names should be displayed instead of IDs whenever possible, as IDs are not meaningful to users. If first and last names are available, indicate that they should be combined into a full name for display (e.g., "with sales rep full names labeling each line").
 - **Default Time Range**: If the user does not specify a time range, default to the last 12 months.
+- **Visual Modifications**: If the user requests visual changes (e.g., "make charts green"), describe the *intended change* (e.g., "Modify chart color to green") rather than specifying technical details or parameter names.
 
 ---
 
diff --git a/api/libs/agents/src/tools/categories/planning_tools/create_plan_straightforward.rs b/api/libs/agents/src/tools/categories/planning_tools/create_plan_straightforward.rs
index 0ad731ecf..d3baaea53 100644
--- a/api/libs/agents/src/tools/categories/planning_tools/create_plan_straightforward.rs
+++ b/api/libs/agents/src/tools/categories/planning_tools/create_plan_straightforward.rs
@@ -160,6 +160,7 @@ Add context like assumptions, limitations, or acknowledge unsupported aspects of
 - **Use Names instead of IDs**: When visualizations or tables include things like people, customers, vendors, products, categories, etc, you should display names instead of IDs (if names are included in the available datasets). IDs are not meaningful to users. For people, you should combine first and last names if they are available.
 - **Default to Top 10**: If the user requests the "top", "best", etc of any entity (e.g., products, regions, employees) without specifying a number, default to showing the top 10 in the visualization.
 - **Default Time Range**: If the user does not specify a time range for a visualization, default to the last 12 months.
+- **Visual Modifications**: If the user requests visual changes (e.g., "make charts green"), describe the *intended change* (e.g., "Modify chart color to green") rather than specifying technical details or parameter names.
 
 ---