diff --git a/output/openapi/elasticsearch-openapi.json b/output/openapi/elasticsearch-openapi.json
index ff3f3af4b0..9581aec5ef 100644
--- a/output/openapi/elasticsearch-openapi.json
+++ b/output/openapi/elasticsearch-openapi.json
@@ -25233,7 +25233,8 @@
         "tags": [
           "rollup"
         ],
-        "summary": "Retrieves the configuration, stats, and status of rollup jobs",
+        "summary": "Get rollup job information",
+        "description": "Get the configuration, stats, and status of rollup jobs.\n\nNOTE: This API returns only active (both `STARTED` and `STOPPED`) jobs.\nIf a job was created, ran for a while, then was deleted, the API does not return any details about it.\nFor details about a historical rollup job, the rollup capabilities API may be more useful.",
         "operationId": "rollup-get-jobs",
         "parameters": [
           {
@@ -25251,7 +25252,8 @@
         "tags": [
           "rollup"
         ],
-        "summary": "Creates a rollup job",
+        "summary": "Create a rollup job",
+        "description": "WARNING: From 8.15.0, calling this API in a cluster with no rollup usage will fail with a message about the deprecation and planned removal of rollup features. A cluster either needs to contain a rollup job or a rollup index in order for this API to be allowed to run.\n\nThe rollup job configuration contains all the details about how the job should run, when it indexes documents, and what future queries will be able to run against the rollup index.\n\nThere are three main sections to the job configuration: the logistical details about the job (for example, the cron schedule), the fields that are used for grouping, and what metrics to collect for each group.\n\nJobs are created in a `STOPPED` state. You can start them with the start rollup jobs API.",
         "operationId": "rollup-put-job",
         "parameters": [
           {
@@ -25334,7 +25336,8 @@
         "tags": [
           "rollup"
         ],
-        "summary": "Deletes an existing rollup job",
+        "summary": "Delete a rollup job",
+        "description": "A job must be stopped first before it can be deleted.\nIf you attempt to delete a started job, an error occurs.\nSimilarly, if you attempt to delete a nonexistent job, an exception occurs.\n\nIMPORTANT: When you delete a job, you remove only the process that is actively monitoring and rolling up data.\nThe API does not delete any previously rolled up data.\nThis is by design; a user may wish to roll up a static data set.\nBecause the data set is static, after it has been fully rolled up there is no need to keep the indexing rollup job around (as there will be no new data).\nThus the job can be deleted, leaving behind the rolled up data for analysis.\nIf you wish to also remove the rollup data and the rollup index contains the data for only a single job, you can delete the whole rollup index.\nIf the rollup index stores data from several jobs, you must issue a delete-by-query that targets the rollup job's identifier in the rollup index. For example:\n\n```\nPOST my_rollup_index/_delete_by_query\n{\n  \"query\": {\n    \"term\": {\n      \"_rollup.id\": \"the_rollup_job_id\"\n    }\n  }\n}\n```",
         "operationId": "rollup-delete-job",
         "parameters": [
           {
@@ -25383,7 +25386,8 @@
         "tags": [
           "rollup"
         ],
-        "summary": "Retrieves the configuration, stats, and status of rollup jobs",
+        "summary": "Get rollup job information",
+        "description": "Get the configuration, stats, and status of rollup jobs.\n\nNOTE: This API returns only active (both `STARTED` and `STOPPED`) jobs.\nIf a job was created, ran for a while, then was deleted, the API does not return any details about it.\nFor details about a historical rollup job, the rollup capabilities API may be more useful.",
         "operationId": "rollup-get-jobs-1",
         "responses": {
           "200": {
@@ -25398,7 +25402,8 @@
         "tags": [
           "rollup"
         ],
-        "summary": "Returns the capabilities of any rollup jobs that have been configured for a specific index or index pattern",
+        "summary": "Get the rollup job capabilities",
+        "description": "Get the capabilities of any rollup jobs that have been configured for a specific index or index pattern.\n\nThis API is useful because a rollup job is often configured to rollup only a subset of fields from the source index.\nFurthermore, only certain aggregations can be configured for various fields, leading to a limited subset of functionality depending on that configuration.\nThis API enables you to inspect an index and determine:\n\n1. Does this index have associated rollup data somewhere in the cluster?\n2. If yes to the first question, what fields were rolled up, what aggregations can be performed, and where does the data live?",
         "operationId": "rollup-get-rollup-caps",
         "parameters": [
           {
@@ -25418,7 +25423,8 @@
         "tags": [
           "rollup"
         ],
-        "summary": "Returns the capabilities of any rollup jobs that have been configured for a specific index or index pattern",
+        "summary": "Get the rollup job capabilities",
+        "description": "Get the capabilities of any rollup jobs that have been configured for a specific index or index pattern.\n\nThis API is useful because a rollup job is often configured to rollup only a subset of fields from the source index.\nFurthermore, only certain aggregations can be configured for various fields, leading to a limited subset of functionality depending on that configuration.\nThis API enables you to inspect an index and determine:\n\n1. Does this index have associated rollup data somewhere in the cluster?\n2. If yes to the first question, what fields were rolled up, what aggregations can be performed, and where does the data live?",
         "operationId": "rollup-get-rollup-caps-1",
         "responses": {
           "200": {
@@ -25433,7 +25439,8 @@
         "tags": [
           "rollup"
         ],
-        "summary": "Returns the rollup capabilities of all jobs inside of a rollup index (for example, the index where rollup data is stored)",
+        "summary": "Get the rollup index capabilities",
+        "description": "Get the rollup capabilities of all jobs inside of a rollup index.\nA single rollup index may store the data for multiple rollup jobs and may have a variety of capabilities depending on those jobs. This API enables you to determine:\n\n* What jobs are stored in an index (or indices specified via a pattern)?\n* What target indices were rolled up, what fields were used in those rollups, and what aggregations can be performed on each job?",
         "operationId": "rollup-get-rollup-index-caps",
         "parameters": [
           {
@@ -25471,7 +25478,8 @@
         "tags": [
           "rollup"
         ],
-        "summary": "Enables searching rolled-up data using the standard Query DSL",
+        "summary": "Search rolled-up data",
+        "description": "The rollup search endpoint is needed because, internally, rolled-up documents utilize a different document structure than the original data.\nIt rewrites standard Query DSL into a format that matches the rollup documents then takes the response and rewrites it back to what a client would expect given the original query.",
         "operationId": "rollup-rollup-search",
         "parameters": [
           {
@@ -25498,7 +25506,8 @@
         "tags": [
           "rollup"
         ],
-        "summary": "Enables searching rolled-up data using the standard Query DSL",
+        "summary": "Search rolled-up data",
+        "description": "The rollup search endpoint is needed because, internally, rolled-up documents utilize a different document structure than the original data.\nIt rewrites standard Query DSL into a format that matches the rollup documents then takes the response and rewrites it back to what a client would expect given the original query.",
         "operationId": "rollup-rollup-search-1",
         "parameters": [
           {
@@ -25527,7 +25536,8 @@
         "tags": [
           "rollup"
         ],
-        "summary": "Starts an existing, stopped rollup job",
+        "summary": "Start rollup jobs",
+        "description": "If you try to start a job that does not exist, an exception occurs.\nIf you try to start a job that is already started, nothing happens.",
         "operationId": "rollup-start-job",
         "parameters": [
           {
@@ -25570,7 +25580,8 @@
         "tags": [
           "rollup"
         ],
-        "summary": "Stops an existing, started rollup job",
+        "summary": "Stop rollup jobs",
+        "description": "If you try to stop a job that does not exist, an exception occurs.\nIf you try to stop a job that is already stopped, nothing happens.",
         "operationId": "rollup-stop-job",
         "parameters": [
           {
diff --git a/output/schema/schema.json b/output/schema/schema.json
index 58e5eb1d7d..43f3e2115d 100644
--- a/output/schema/schema.json
+++ b/output/schema/schema.json
@@ -14226,9 +14226,14 @@
           "stability": "experimental"
         }
       },
-      "description": "Deletes an existing rollup job.",
+      "description": "Delete a rollup job.\n\nA job must be stopped before it can be deleted.\nIf you attempt to delete a started job, an error occurs.\nSimilarly, if you attempt to delete a nonexistent job, an exception occurs.\n\nIMPORTANT: When you delete a job, you remove only the process that is actively monitoring and rolling up data.\nThe API does not delete any previously rolled up data.\nThis is by design; a user may wish to roll up a static data set.\nBecause the data set is static, after it has been fully rolled up there is no need to keep the indexing rollup job around (as there will be no new data).\nThus the job can be deleted, leaving behind the rolled up data for analysis.\nIf you wish to also remove the rollup data and the rollup index contains the data for only a single job, you can delete the whole rollup index.\nIf the rollup index stores data from several jobs, you must issue a delete-by-query that targets the rollup job's identifier in the rollup index. For example:\n\n```\nPOST my_rollup_index/_delete_by_query\n{\n  \"query\": {\n    \"term\": {\n      \"_rollup.id\": \"the_rollup_job_id\"\n    }\n  }\n}\n```",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/master/rollup-delete-job.html",
       "name": "rollup.delete_job",
+      "privileges": {
+        "cluster": [
+          "manage_rollup"
+        ]
+      },
       "request": {
         "name": "Request",
         "namespace": "rollup.delete_job"
@@ -14257,9 +14262,14 @@
           "stability": "experimental"
         }
       },
-      "description": "Retrieves the configuration, stats, and status of rollup jobs.",
+      "description": "Get rollup job information.\nGet the configuration, stats, and status of rollup jobs.\n\nNOTE: This API returns only active (both `STARTED` and `STOPPED`) jobs.\nIf a job was created, ran for a while, then was deleted, the API does not return any details about it.\nFor details about a historical rollup job, the rollup capabilities API may be more useful.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/master/rollup-get-job.html",
       "name": "rollup.get_jobs",
+      "privileges": {
+        "cluster": [
+          "monitor_rollup"
+        ]
+      },
       "request": {
         "name": "Request",
         "namespace": "rollup.get_jobs"
@@ -14294,9 +14304,14 @@
           "stability": "experimental"
         }
       },
-      "description": "Returns the capabilities of any rollup jobs that have been configured for a specific index or index pattern.",
+      "description": "Get the rollup job capabilities.\nGet the capabilities of any rollup jobs that have been configured for a specific index or index pattern.\n\nThis API is useful because a rollup job is often configured to rollup only a subset of fields from the source index.\nFurthermore, only certain aggregations can be configured for various fields, leading to a limited subset of functionality depending on that configuration.\nThis API enables you to inspect an index and determine:\n\n1. Does this index have associated rollup data somewhere in the cluster?\n2. If yes to the first question, what fields were rolled up, what aggregations can be performed, and where does the data live?",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/master/rollup-get-rollup-caps.html",
       "name": "rollup.get_rollup_caps",
+      "privileges": {
+        "cluster": [
+          "monitor_rollup"
+        ]
+      },
       "request": {
         "name": "Request",
         "namespace": "rollup.get_rollup_caps"
@@ -14331,9 +14346,14 @@
           "stability": "experimental"
         }
       },
-      "description": "Returns the rollup capabilities of all jobs inside of a rollup index (for example, the index where rollup data is stored).",
+      "description": "Get the rollup index capabilities.\nGet the rollup capabilities of all jobs inside of a rollup index.\nA single rollup index may store the data for multiple rollup jobs and may have a variety of capabilities depending on those jobs. This API enables you to determine:\n\n* What jobs are stored in an index (or indices specified via a pattern)?\n* What target indices were rolled up, what fields were used in those rollups, and what aggregations can be performed on each job?",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/master/rollup-get-rollup-index-caps.html",
       "name": "rollup.get_rollup_index_caps",
+      "privileges": {
+        "index": [
+          "read"
+        ]
+      },
       "request": {
         "name": "Request",
         "namespace": "rollup.get_rollup_index_caps"
@@ -14362,7 +14382,7 @@
           "stability": "experimental"
         }
       },
-      "description": "Creates a rollup job.",
+      "description": "Create a rollup job.\n\nWARNING: From 8.15.0, calling this API in a cluster with no rollup usage will fail with a message about the deprecation and planned removal of rollup features. A cluster needs to contain either a rollup job or a rollup index in order for this API to be allowed to run.\n\nThe rollup job configuration contains all the details about how the job should run, when it indexes documents, and what future queries will be able to run against the rollup index.\n\nThere are three main sections to the job configuration: the logistical details about the job (for example, the cron schedule), the fields that are used for grouping, and what metrics to collect for each group.\n\nJobs are created in a `STOPPED` state. You can start them with the start rollup jobs API.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/master/rollup-put-job.html",
       "name": "rollup.put_job",
       "privileges": {
@@ -14402,7 +14422,7 @@
           "stability": "experimental"
         }
       },
-      "description": "Enables searching rolled-up data using the standard Query DSL.",
+      "description": "Search rolled-up data.\nThe rollup search endpoint is needed because, internally, rolled-up documents utilize a different document structure than the original data.\nIt rewrites standard Query DSL into a format that matches the rollup documents then takes the response and rewrites it back to what a client would expect given the original query.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/master/rollup-search.html",
       "name": "rollup.rollup_search",
       "request": {
@@ -14437,9 +14457,14 @@
           "stability": "experimental"
         }
       },
-      "description": "Starts an existing, stopped rollup job.",
+      "description": "Start rollup jobs.\nIf you try to start a job that does not exist, an exception occurs.\nIf you try to start a job that is already started, nothing happens.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/master/rollup-start-job.html",
       "name": "rollup.start_job",
+      "privileges": {
+        "cluster": [
+          "manage_rollup"
+        ]
+      },
       "request": {
         "name": "Request",
         "namespace": "rollup.start_job"
@@ -14468,9 +14493,14 @@
           "stability": "experimental"
         }
       },
-      "description": "Stops an existing, started rollup job.",
+      "description": "Stop rollup jobs.\nIf you try to stop a job that does not exist, an exception occurs.\nIf you try to stop a job that is already stopped, nothing happens.",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/master/rollup-stop-job.html",
       "name": "rollup.stop_job",
+      "privileges": {
+        "cluster": [
+          "manage_rollup"
+        ]
+      },
       "request": {
         "name": "Request",
         "namespace": "rollup.stop_job"
@@ -185624,7 +185654,7 @@
       "body": {
         "kind": "no_body"
       },
-      "description": "Deletes an existing rollup job.",
+      "description": "Delete a rollup job.\n\nA job must be stopped before it can be deleted.\nIf you attempt to delete a started job, an error occurs.\nSimilarly, if you attempt to delete a nonexistent job, an exception occurs.\n\nIMPORTANT: When you delete a job, you remove only the process that is actively monitoring and rolling up data.\nThe API does not delete any previously rolled up data.\nThis is by design; a user may wish to roll up a static data set.\nBecause the data set is static, after it has been fully rolled up there is no need to keep the indexing rollup job around (as there will be no new data).\nThus the job can be deleted, leaving behind the rolled up data for analysis.\nIf you wish to also remove the rollup data and the rollup index contains the data for only a single job, you can delete the whole rollup index.\nIf the rollup index stores data from several jobs, you must issue a delete-by-query that targets the rollup job's identifier in the rollup index. For example:\n\n```\nPOST my_rollup_index/_delete_by_query\n{\n  \"query\": {\n    \"term\": {\n      \"_rollup.id\": \"the_rollup_job_id\"\n    }\n  }\n}\n```",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -185650,7 +185680,7 @@
         }
       ],
       "query": [],
-      "specLocation": "rollup/delete_job/DeleteRollupJobRequest.ts#L23-L35"
+      "specLocation": "rollup/delete_job/DeleteRollupJobRequest.ts#L23-L59"
     },
     {
       "kind": "response",
@@ -185723,7 +185753,7 @@
       "body": {
         "kind": "no_body"
       },
-      "description": "Retrieves the configuration, stats, and status of rollup jobs.",
+      "description": "Get rollup job information.\nGet the configuration, stats, and status of rollup jobs.\n\nNOTE: This API returns only active (both `STARTED` and `STOPPED`) jobs.\nIf a job was created, ran for a while, then was deleted, the API does not return any details about it.\nFor details about a historical rollup job, the rollup capabilities API may be more useful.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -185749,7 +185779,7 @@
         }
       ],
       "query": [],
-      "specLocation": "rollup/get_jobs/GetRollupJobRequest.ts#L23-L36"
+      "specLocation": "rollup/get_jobs/GetRollupJobRequest.ts#L23-L42"
     },
     {
       "kind": "response",
@@ -186149,7 +186179,7 @@
       "body": {
         "kind": "no_body"
       },
-      "description": "Returns the capabilities of any rollup jobs that have been configured for a specific index or index pattern.",
+      "description": "Get the rollup job capabilities.\nGet the capabilities of any rollup jobs that have been configured for a specific index or index pattern.\n\nThis API is useful because a rollup job is often configured to rollup only a subset of fields from the source index.\nFurthermore, only certain aggregations can be configured for various fields, leading to a limited subset of functionality depending on that configuration.\nThis API enables you to inspect an index and determine:\n\n1. Does this index have associated rollup data somewhere in the cluster?\n2. If yes to the first question, what fields were rolled up, what aggregations can be performed, and where does the data live?",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -186175,7 +186205,7 @@
         }
       ],
       "query": [],
-      "specLocation": "rollup/get_rollup_caps/GetRollupCapabilitiesRequest.ts#L23-L36"
+      "specLocation": "rollup/get_rollup_caps/GetRollupCapabilitiesRequest.ts#L23-L45"
     },
     {
       "kind": "response",
@@ -186373,7 +186403,7 @@
       "body": {
         "kind": "no_body"
       },
-      "description": "Returns the rollup capabilities of all jobs inside of a rollup index (for example, the index where rollup data is stored).",
+      "description": "Get the rollup index capabilities.\nGet the rollup capabilities of all jobs inside of a rollup index.\nA single rollup index may store the data for multiple rollup jobs and may have a variety of capabilities depending on those jobs. This API enables you to determine:\n\n* What jobs are stored in an index (or indices specified via a pattern)?\n* What target indices were rolled up, what fields were used in those rollups, and what aggregations can be performed on each job?",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -186399,7 +186429,7 @@
         }
       ],
       "query": [],
-      "specLocation": "rollup/get_rollup_index_caps/GetRollupIndexCapabilitiesRequest.ts#L23-L36"
+      "specLocation": "rollup/get_rollup_index_caps/GetRollupIndexCapabilitiesRequest.ts#L23-L42"
     },
     {
       "kind": "response",
@@ -186650,7 +186680,7 @@
           }
         ]
       },
-      "description": "Creates a rollup job.",
+      "description": "Create a rollup job.\n\nWARNING: From 8.15.0, calling this API in a cluster with no rollup usage will fail with a message about the deprecation and planned removal of rollup features. A cluster needs to contain either a rollup job or a rollup index in order for this API to be allowed to run.\n\nThe rollup job configuration contains all the details about how the job should run, when it indexes documents, and what future queries will be able to run against the rollup index.\n\nThere are three main sections to the job configuration: the logistical details about the job (for example, the cron schedule), the fields that are used for grouping, and what metrics to collect for each group.\n\nJobs are created in a `STOPPED` state. You can start them with the start rollup jobs API.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -186676,7 +186706,7 @@
         }
       ],
       "query": [],
-      "specLocation": "rollup/put_job/CreateRollupJobRequest.ts#L27-L89"
+      "specLocation": "rollup/put_job/CreateRollupJobRequest.ts#L27-L97"
     },
     {
       "kind": "response",
@@ -186756,7 +186786,7 @@
           }
         ]
       },
-      "description": "Enables searching rolled-up data using the standard Query DSL.",
+      "description": "Search rolled-up data.\nThe rollup search endpoint is needed because, internally, rolled-up documents utilize a different document structure than the original data.\nIt rewrites standard Query DSL into a format that matches the rollup documents then takes the response and rewrites it back to what a client would expect given the original query.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -186807,7 +186837,7 @@
           }
         }
       ],
-      "specLocation": "rollup/rollup_search/RollupSearchRequest.ts#L27-L57"
+      "specLocation": "rollup/rollup_search/RollupSearchRequest.ts#L27-L59"
     },
     {
       "kind": "response",
@@ -186922,7 +186952,7 @@
       "body": {
         "kind": "no_body"
       },
-      "description": "Starts an existing, stopped rollup job.",
+      "description": "Start rollup jobs.\nIf you try to start a job that does not exist, an exception occurs.\nIf you try to start a job that is already started, nothing happens.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -186948,7 +186978,7 @@
         }
       ],
       "query": [],
-      "specLocation": "rollup/start_job/StartRollupJobRequest.ts#L23-L35"
+      "specLocation": "rollup/start_job/StartRollupJobRequest.ts#L23-L38"
     },
     {
       "kind": "response",
@@ -186982,7 +187012,7 @@
       "body": {
         "kind": "no_body"
       },
-      "description": "Stops an existing, started rollup job.",
+      "description": "Stop rollup jobs.\nIf you try to stop a job that does not exist, an exception occurs.\nIf you try to stop a job that is already stopped, nothing happens.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -187035,7 +187065,7 @@
           }
         }
       ],
-      "specLocation": "rollup/stop_job/StopRollupJobRequest.ts#L24-L50"
+      "specLocation": "rollup/stop_job/StopRollupJobRequest.ts#L24-L53"
     },
     {
       "kind": "response",
diff --git a/specification/rollup/delete_job/DeleteRollupJobRequest.ts b/specification/rollup/delete_job/DeleteRollupJobRequest.ts
index e2d467fe3d..eef578b63d 100644
--- a/specification/rollup/delete_job/DeleteRollupJobRequest.ts
+++ b/specification/rollup/delete_job/DeleteRollupJobRequest.ts
@@ -21,9 +21,33 @@ import { RequestBase } from '@_types/Base'
 import { Id } from '@_types/common'
 
 /**
- * Deletes an existing rollup job.
+ * Delete a rollup job.
+ *
+ * A job must be stopped before it can be deleted.
+ * If you attempt to delete a started job, an error occurs.
+ * Similarly, if you attempt to delete a nonexistent job, an exception occurs.
+ *
+ * IMPORTANT: When you delete a job, you remove only the process that is actively monitoring and rolling up data.
+ * The API does not delete any previously rolled up data.
+ * This is by design; a user may wish to roll up a static data set.
+ * Because the data set is static, after it has been fully rolled up there is no need to keep the indexing rollup job around (as there will be no new data).
+ * Thus the job can be deleted, leaving behind the rolled up data for analysis.
+ * If you wish to also remove the rollup data and the rollup index contains the data for only a single job, you can delete the whole rollup index.
+ * If the rollup index stores data from several jobs, you must issue a delete-by-query that targets the rollup job's identifier in the rollup index. For example:
+ *
+ * ```
+ * POST my_rollup_index/_delete_by_query
+ * {
+ *   "query": {
+ *     "term": {
+ *       "_rollup.id": "the_rollup_job_id"
+ *     }
+ *   }
+ * }
+ * ```
  * @rest_spec_name rollup.delete_job
  * @availability stack since=6.3.0 stability=experimental
+ * @cluster_privileges manage_rollup
  */
 export interface Request extends RequestBase {
   path_parts: {
diff --git a/specification/rollup/get_jobs/GetRollupJobRequest.ts b/specification/rollup/get_jobs/GetRollupJobRequest.ts
index fa990bf94f..6e69d18a09 100644
--- a/specification/rollup/get_jobs/GetRollupJobRequest.ts
+++ b/specification/rollup/get_jobs/GetRollupJobRequest.ts
@@ -21,9 +21,15 @@ import { RequestBase } from '@_types/Base'
 import { Id } from '@_types/common'
 
 /**
- * Retrieves the configuration, stats, and status of rollup jobs.
+ * Get rollup job information.
+ * Get the configuration, stats, and status of rollup jobs.
+ *
+ * NOTE: This API returns only active (both `STARTED` and `STOPPED`) jobs.
+ * If a job was created, ran for a while, then was deleted, the API does not return any details about it.
+ * For details about a historical rollup job, the rollup capabilities API may be more useful.
  * @rest_spec_name rollup.get_jobs
  * @availability stack since=6.3.0 stability=experimental
+ * @cluster_privileges monitor_rollup
  */
 export interface Request extends RequestBase {
   path_parts: {
diff --git a/specification/rollup/get_rollup_caps/GetRollupCapabilitiesRequest.ts b/specification/rollup/get_rollup_caps/GetRollupCapabilitiesRequest.ts
index bd7673d72a..d579f5ae9a 100644
--- a/specification/rollup/get_rollup_caps/GetRollupCapabilitiesRequest.ts
+++ b/specification/rollup/get_rollup_caps/GetRollupCapabilitiesRequest.ts
@@ -21,9 +21,18 @@ import { RequestBase } from '@_types/Base'
 import { Id } from '@_types/common'
 
 /**
- * Returns the capabilities of any rollup jobs that have been configured for a specific index or index pattern.
+ * Get the rollup job capabilities.
+ * Get the capabilities of any rollup jobs that have been configured for a specific index or index pattern.
+ *
+ * This API is useful because a rollup job is often configured to rollup only a subset of fields from the source index.
+ * Furthermore, only certain aggregations can be configured for various fields, leading to a limited subset of functionality depending on that configuration.
+ * This API enables you to inspect an index and determine:
+ *
+ * 1. Does this index have associated rollup data somewhere in the cluster?
+ * 2. If yes to the first question, what fields were rolled up, what aggregations can be performed, and where does the data live?
  * @rest_spec_name rollup.get_rollup_caps
  * @availability stack since=6.3.0 stability=experimental
+ * @cluster_privileges monitor_rollup
  */
 export interface Request extends RequestBase {
   path_parts: {
diff --git a/specification/rollup/get_rollup_index_caps/GetRollupIndexCapabilitiesRequest.ts b/specification/rollup/get_rollup_index_caps/GetRollupIndexCapabilitiesRequest.ts
index 36d77bd4c2..4ff08efcf4 100644
--- a/specification/rollup/get_rollup_index_caps/GetRollupIndexCapabilitiesRequest.ts
+++ b/specification/rollup/get_rollup_index_caps/GetRollupIndexCapabilitiesRequest.ts
@@ -21,9 +21,15 @@ import { RequestBase } from '@_types/Base'
 import { Ids } from '@_types/common'
 
 /**
- * Returns the rollup capabilities of all jobs inside of a rollup index (for example, the index where rollup data is stored).
+ * Get the rollup index capabilities.
+ * Get the rollup capabilities of all jobs inside of a rollup index.
+ * A single rollup index may store the data for multiple rollup jobs and may have a variety of capabilities depending on those jobs. This API enables you to determine:
+ *
+ * * What jobs are stored in an index (or indices specified via a pattern)?
+ * * What target indices were rolled up, what fields were used in those rollups, and what aggregations can be performed on each job?
  * @rest_spec_name rollup.get_rollup_index_caps
  * @availability stack since=6.4.0 stability=experimental
+ * @index_privileges read
  */
 export interface Request extends RequestBase {
   path_parts: {
diff --git a/specification/rollup/put_job/CreateRollupJobRequest.ts b/specification/rollup/put_job/CreateRollupJobRequest.ts
index 6f00c8cb9a..b16206b85d 100644
--- a/specification/rollup/put_job/CreateRollupJobRequest.ts
+++ b/specification/rollup/put_job/CreateRollupJobRequest.ts
@@ -25,7 +25,15 @@ import { integer } from '@_types/Numeric'
 import { Duration } from '@_types/Time'
 
 /**
- * Creates a rollup job.
+ * Create a rollup job.
+ *
+ * WARNING: From 8.15.0, calling this API in a cluster with no rollup usage will fail with a message about the deprecation and planned removal of rollup features. A cluster needs to contain either a rollup job or a rollup index in order for this API to be allowed to run.
+ *
+ * The rollup job configuration contains all the details about how the job should run, when it indexes documents, and what future queries will be able to run against the rollup index.
+ *
+ * There are three main sections to the job configuration: the logistical details about the job (for example, the cron schedule), the fields that are used for grouping, and what metrics to collect for each group.
+ *
+ * Jobs are created in a `STOPPED` state. You can start them with the start rollup jobs API.
  * @rest_spec_name rollup.put_job
  * @availability stack since=6.3.0 stability=experimental
  * @cluster_privileges manage, manage_rollup
diff --git a/specification/rollup/rollup_search/RollupSearchRequest.ts b/specification/rollup/rollup_search/RollupSearchRequest.ts
index 7f27d9b54f..4261604f07 100644
--- a/specification/rollup/rollup_search/RollupSearchRequest.ts
+++ b/specification/rollup/rollup_search/RollupSearchRequest.ts
@@ -25,7 +25,9 @@ import { integer } from '@_types/Numeric'
 import { QueryContainer } from '@_types/query_dsl/abstractions'
 
 /**
- * Enables searching rolled-up data using the standard Query DSL.
+ * Search rolled-up data.
+ * The rollup search endpoint is needed because, internally, rolled-up documents utilize a different document structure than the original data.
+ * It rewrites standard Query DSL into a format that matches the rollup documents then takes the response and rewrites it back to what a client would expect given the original query.
  * @rest_spec_name rollup.rollup_search
  * @availability stack since=6.3.0 stability=experimental
  */
diff --git a/specification/rollup/start_job/StartRollupJobRequest.ts b/specification/rollup/start_job/StartRollupJobRequest.ts
index 1ae1c98aaa..229aa2a56f 100644
--- a/specification/rollup/start_job/StartRollupJobRequest.ts
+++ b/specification/rollup/start_job/StartRollupJobRequest.ts
@@ -21,9 +21,12 @@ import { RequestBase } from '@_types/Base'
 import { Id } from '@_types/common'
 
 /**
- * Starts an existing, stopped rollup job.
+ * Start rollup jobs.
+ * If you try to start a job that does not exist, an exception occurs.
+ * If you try to start a job that is already started, nothing happens.
  * @rest_spec_name rollup.start_job
  * @availability stack since=6.3.0 stability=experimental
+ * @cluster_privileges manage_rollup
  */
 export interface Request extends RequestBase {
   path_parts: {
diff --git a/specification/rollup/stop_job/StopRollupJobRequest.ts b/specification/rollup/stop_job/StopRollupJobRequest.ts
index a8824f19e3..88541dea0c 100644
--- a/specification/rollup/stop_job/StopRollupJobRequest.ts
+++ b/specification/rollup/stop_job/StopRollupJobRequest.ts
@@ -22,9 +22,12 @@ import { Id } from '@_types/common'
 import { Duration } from '@_types/Time'
 
 /**
- * Stops an existing, started rollup job.
+ * Stop rollup jobs.
+ * If you try to stop a job that does not exist, an exception occurs.
+ * If you try to stop a job that is already stopped, nothing happens.
  * @rest_spec_name rollup.stop_job
  * @availability stack since=6.3.0 stability=experimental
+ * @cluster_privileges manage_rollup
  */
 export interface Request extends RequestBase {
   path_parts: {