diff --git a/source/_docs/tools/dev-tools.markdown b/source/_docs/tools/dev-tools.markdown
index babe4cde4d7..3beafd151f8 100644
--- a/source/_docs/tools/dev-tools.markdown
+++ b/source/_docs/tools/dev-tools.markdown
@@ -126,3 +126,16 @@ Another use of the {% my developer_statistics title="statistics developer tool"
 icon. Use date & time to search for the incorrect data point and adjust the value.
 
 ![Screenshot showing adjusting the long-term statistic history value](/images/blog/2022-04/adjust-statistics.png)
+
+## Assist
+
+The **Assist** tab lets you see how Home Assistant's Assist processes a sentence.
+
+If no matching intent is found, then Assist is unable to interpret the sentence. If a matching intent was found, information is provided on the action that will be performed on which entities. The example below shows how the following sentence was parsed: *what lights are on in the office*. 
+- Assist found a matching intent: *HassGetState*.
+- It found entities matching the domain: *lights*.
+- The lights have the state *on*.
+- The lights are in the area *office*. 
+- The targets are the narrowed-down entities in scope.
+
+![Example use of assist developer tools](/images/docs/developer-tools/Assist.png)
diff --git a/source/images/docs/developer-tools/Assist.png b/source/images/docs/developer-tools/Assist.png
new file mode 100644
index 00000000000..61bd212c468
Binary files /dev/null and b/source/images/docs/developer-tools/Assist.png differ