diff --git a/output/schema/schema-serverless.json b/output/schema/schema-serverless.json
index c82ab82184..d87f5a0978 100644
--- a/output/schema/schema-serverless.json
+++ b/output/schema/schema-serverless.json
@@ -9325,7 +9325,7 @@
           "stability": "experimental"
         }
       },
-      "description": "Get task information.\nReturns information about the tasks currently executing in the cluster.",
+      "description": "Get task information.\nGet information about a task currently running in the cluster.",
       "docId": "tasks",
       "docUrl": "https://www.elastic.co/guide/en/elasticsearch/reference/{branch}/tasks.html",
       "name": "tasks.get",
@@ -41799,7 +41799,7 @@
       "body": {
         "kind": "no_body"
       },
-      "description": "Get task information.\nReturns information about the tasks currently executing in the cluster.",
+      "description": "Get task information.\nGet information about a task currently running in the cluster.",
       "inherits": {
         "type": {
           "name": "RequestBase",
@@ -104918,6 +104918,7 @@
           }
         },
         {
+          "description": "Human readable text that identifies the particular request that the task is performing.\nFor example, it might identify the search request being performed by a search task.\nOther kinds of tasks have different descriptions, like `_reindex` which has the source and the destination, or `_bulk` which just has the number of requests and the destination indices.\nMany requests will have only an empty description because more detailed information about the request is not easily available or particularly helpful in identifying the request.",
           "name": "description",
           "required": false,
           "type": {
@@ -105024,7 +105025,7 @@
           }
         },
         {
-          "description": "Task status information can vary wildly from task to task.",
+          "description": "The internal status of the task, which varies from task to task.\nThe format also varies.\nWhile the goal is to keep the status for a particular task consistent from version to version, this is not always possible because sometimes the implementation changes.\nFields might be removed from the status for a particular request so any parsing you do of the status might break in minor releases.",
           "name": "status",
           "required": false,
           "type": {
@@ -105054,7 +105055,7 @@
           }
         }
       ],
-      "specLocation": "tasks/_types/TaskInfo.ts#L32-L47"
+      "specLocation": "tasks/_types/TaskInfo.ts#L32-L58"
     },
     {
       "inherits": {
@@ -105892,7 +105893,7 @@
         "name": "XPackCategory",
         "namespace": "xpack.info"
       },
-      "specLocation": "xpack/info/XPackInfoRequest.ts#L44-L48"
+      "specLocation": "xpack/info/XPackInfoRequest.ts#L49-L53"
     },
     {
       "attachedBehaviors": [