docs: close the remaining description and hint-orientation gaps

agent-security/agentic-security-with-snyk-studio/README.md

@@ -1,4 +1,7 @@
 ---
+description: >-
+  How Snyk Studio embeds security directives into AI-assisted development
+  workflows
 nav_context: agnostic
 ---
 

developer-tools/snyk-api/api-end-of-life-eol-process-and-migration-guides/guides-to-migration/list-all-projects-v1-api-to-rest-api-migration-guide-completed-migration.md

@@ -2,9 +2,10 @@
 description: Migration guide from the V1 List all Projects endpoint to the REST API
 nav_context: agnostic
 ---
-
 # List all Projects V1 API to REST API migration guide (completed migration)
 
+This guide maps the retired List all Projects V1 API endpoint to its REST API equivalent. The migration is complete, so use it as a reference for reading older integrations rather than as a task to perform.
+
 {% hint style="warning" %}
 **End of life**
 

developer-tools/snyk-api/api-end-of-life-eol-process-and-migration-guides/guides-to-migration/v1-reporting-issues-and-v1-aggregated-issues-apis-to-rest-issues-api-migration-guide.md

@@ -3,9 +3,10 @@ hidden: true
 description: Migration guide from the V1 Issues APIs to the REST Issues API
 nav_context: agnostic
 ---
-
 # V1 Issues APIs to REST Issues API migration guide
 
+This guide maps the V1 Issues endpoints to the REST Issues API, and describes what changes in the request and the response when you migrate.
+
 {% hint style="info" %}
 This page applies to the following V1  API endpoints:
 

developer-tools/snyk-ci-cd-integrations/README.md

@@ -4,9 +4,10 @@ description: >-
   How to integrate Snyk into CI/CD pipelines, with the Snyk CLI recommended for
   flexibility
 ---
-
 # Snyk CI/CDs
 
+Snyk integrates with continuous integration and continuous delivery (CI/CD) pipelines so you can fail a build, or report on it, when a scan finds issues.
+
 {% hint style="info" %}
 Snyk recommends using the CLI for CI/CD integrations for the following reasons:
 

developer-tools/snyk-cli/commands/fix.md

@@ -1,3 +1,9 @@
+---
+description: >-
+  The snyk fix --agentic command, which applies and verifies vulnerability
+  fixes
+---
+
 # Fix (`snyk fix --agentic`)
 
 {% hint style="info" %}

developer-tools/snyk-cli/commands/secrets-test.md

@@ -1,3 +1,9 @@
+---
+description: >-
+  The snyk secrets test command, which scans for hard-coded secrets and
+  credentials
+---
+
 # Secrets test
 
 ## Prerequisites

developer-tools/snyk-ide-plugins-and-extensions/compatibility-matrix.md

@@ -1,3 +1,9 @@
+---
+description: >-
+  Compatible Snyk CLI version ranges for each IDE plugin version released in
+  the past 12 months
+---
+
 # IDE Plugin Compatibility Matrix
 
 This matrix shows the compatible CLI version range for each IDE plugin version released in the past 12 months.

platform-administration/enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/install-and-configure-broker-using-docker.md

@@ -2,9 +2,10 @@
 description: How to install and configure the Classic Snyk Broker using Docker
 nav_context: agnostic
 ---
-
 # Install and configure Broker using Docker
 
+Run Snyk Broker as a Docker container to connect Snyk to systems inside your network without exposing them to the internet.
+
 {% hint style="info" %}
 [Broker version 4.205.1](https://github.com/snyk/broker/blob/cb4f89e05eb42605f076321b952cdb7e57bf4111/config.default.json#L8) has been [released](https://updates.snyk.io). In this version, all `ACCEPT` rule flags will be enabled by default. This reduces needed configuration. If you do not want a specific `ACCEPT` rule flag to be enabled, you can opt out of the default `ACCEPT` all behavior by adding `ACCEPT_=false` to your Broker client configuration.
 {% endhint %}

platform-administration/enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/install-and-configure-broker-using-helm.md

@@ -2,9 +2,10 @@
 description: How to install and configure the Classic Snyk Broker using Helm
 nav_context: agnostic
 ---
-
 # Install and configure Broker using Helm
 
+Deploy Snyk Broker to a Kubernetes cluster with the Snyk Broker Helm chart to connect Snyk to systems inside your network.
+
 {% hint style="info" %}
 [Broker version 4.205.1](https://github.com/snyk/broker/blob/cb4f89e05eb42605f076321b952cdb7e57bf4111/config.default.json#L8) has been [released](https://updates.snyk.io). In this version, all `ACCEPT` rule flags will be enabled by default. This reduces needed configuration. If you do not want a specific `ACCEPT` rule flag to be enabled, you can opt out of the default `ACCEPT` all behavior by adding `ACCEPT_=false` to your Broker client configuration.
 {% endhint %}

scan-fix-and-prevent/scan-with-snyk/snyk-api-web/configure-targets/verify-domain-ownership/verify-with-dns-txt.md

@@ -1,4 +1,7 @@
 ---
+description: >-
+  How to verify domain ownership for a Snyk API & Web target with a DNS TXT
+  record
 nav_context: classic
 ---
 

scan-fix-and-prevent/scan-with-snyk/snyk-iac/scan-your-iac-source-code/scan-terraform-files/terraform-aws-provider-support.md

@@ -2,9 +2,10 @@
 description: Support and limitations for the Terraform AWS provider.
 nav_context: agnostic
 ---
-
 # Terraform AWS Provider support
 
+Snyk IaC scans Terraform files that use the AWS provider. Version 4.0.0 of the provider changed how S3 buckets are defined, which affects how Snyk reports issues against them.
+
 {% hint style="success" %}
 Version 4.0.0 of the AWS Terraform Provider introduced changes in how S3 services are defined. With v4.0, the definition of S3 services is now spread across several resource blocks within Terraform. If you defined an instance of an S3 bucket across multiple files, this update is a breaking change and may have negatively impacted your security results from Snyk IaC.
 {% endhint %}