docs(config): add description field with Rocky AI context to all check config pages

Author: pmallol

detect/synthetic-monitoring/api-checks/configuration.mdx

@@ -212,4 +212,12 @@ This list shows all content types that we scrub from the response data.
 |`video/x-ms-wmv`|
 |`video/x-msvideo`|
 |`video/x-flv`|
-|`video/webm`|
+|`video/webm`|
+
+## Additional Settings
+
+* **Name:** Give your check a clear name to identify it in dashboards and alerts
+* **Description:** Add context about what this check does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/platform/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview)
+* **Tags:** Use tags to organize checks across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview)
+* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries)
+* **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations

detect/synthetic-monitoring/playwright-checks/configuration.mdx

@@ -102,6 +102,10 @@ A Playwright Check Suite inherits multiple properties from [the abstract `Check`
 
 Check out [the reference documentation](/constructs/project#param-checks-playwright-checks) for more information on these settings.
 
+<Tip>
+Use the `description` property to add context about what your check does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/platform/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview).
+</Tip>
+
 <Note>
 **Checks' Retry strategy is not applicable for Playwright checks.** Playwright includes its own retry features that can be set up directly in your `playwright.config.ts/js` file with the [`retries`](https://playwright.dev/docs/test-retries) option. This allows for more detailed management of test retries within Playwright, when your check runs.
 </Note>

detect/uptime-monitoring/dns-monitors/configuration.mdx

@@ -323,6 +323,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours):
 ### Additional Settings
 
 * **Name:** Give your monitor a clear name to identify it in dashboards and alerts
+* **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/platform/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview)
 * **Tags:** Use tags to organize monitors across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview)
 * **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries)
 * **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations

detect/uptime-monitoring/heartbeat-monitors/configuration.mdx

@@ -2,4 +2,12 @@
 title: Heartbeat Configuration
 description:  Ensure your critical automated processes are running as expected.
 sidebarTitle: Configuration
----
+---
+
+### Additional Settings
+
+* **Name:** Give your monitor a clear name to identify it in dashboards and alerts
+* **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/platform/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview)
+* **Tags:** Use tags to organize monitors across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview)
+* **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries)
+* **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations

detect/uptime-monitoring/icmp-monitors/configuration.mdx

@@ -101,6 +101,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours):
 ### Additional Settings
 
 * **Name:** Give your monitor a clear name to identify it in dashboards and alerts
+* **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/platform/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview)
 * **Tags:** Use tags to organize monitors across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview)
 * **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries)
 * **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations

detect/uptime-monitoring/tcp-monitors/configuration.mdx

@@ -65,6 +65,7 @@ Set how often the monitor runs (every 10 seconds to 24 hours):
 ### Additional Settings
 
 * **Name:** Give your monitor a clear name to identify it in dashboards and alerts
+* **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/platform/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview)
 * **Tags:** Use tags to organize monitors across dashboards and [maintenance windows](/communicate/maintenance-windows/overview)
 * **Retries:** Define how failed runs should be retried. See [retry strategies](/communicate/alerts/retries)
 * **Alerting:** Configure your [alert settings](/communicate/alerts/configuration), [alert channels](/communicate/alerts/channels), or set up [webhooks](/integrations/alerts/webhooks) for custom integrations

detect/uptime-monitoring/url-monitors/configuration.mdx

@@ -139,6 +139,12 @@ Define where notifications are sent when checks fail or recover. Additional chan
 **Global Alert Settings**: By default, monitors inherit your account's notification preferences. Select "Use specific notification settings" to customize alerts for individual monitors.
 </Note>
 
+### Additional Settings
+
+* **Name:** Give your monitor a clear name to identify it in dashboards and alerts
+* **Description:** Add context about what this monitor does and why it matters. Supports markdown, max 500 characters. When a failure occurs, [Rocky AI](/platform/rocky-ai) uses the description to provide more accurate [root cause and user impact analysis](/resolve/ai-root-cause-analysis/overview)
+* **Tags:** Use tags to organize monitors across [dashboards](/communicate/dashboards/overview/) and [maintenance windows](/communicate/maintenance-windows/overview)
+