@webitel/api-services 26.12.3 → 26.12.4

package/src/gen-wire/call-service/call-service.zod.ts

@@ -489,6 +489,7 @@ export const SearchHistoryCallQueryParams = zod.object({
 			]),
 		)
 		.optional(),
+	hide_number: zod.boolean().optional(),
 });
 
 export const searchHistoryCallResponseItemsItemFilesItemTypeDefault = `file_type_empty`;
@@ -863,6 +864,7 @@ export const SearchHistoryCallPostBody = zod.object({
 	has_file: zod.boolean().optional(),
 	has_transcript: zod.boolean().optional(),
 	has_transfer: zod.boolean().optional(),
+	hide_number: zod.boolean().optional(),
 	id: zod.array(zod.string()).optional(),
 	member_id: zod.array(zod.string()).optional(),
 	missed: zod.boolean().optional(),

package/src/gen-wire/cases/cases.zod.ts

@@ -1362,17 +1362,42 @@ export const ExportCasesQueryParams = zod.object({
 export const ExportCasesResponse = zod.object({
 	error: zod
 		.object({
-			code: zod.int().optional(),
+			code: zod
+				.int()
+				.optional()
+				.describe(
+					'The status code, which should be an enum value of\n[google.rpc.Code][google.rpc.Code].',
+				),
 			details: zod
 				.array(
-					zod.object({
-						'@type': zod.string().optional(),
-					}),
+					zod
+						.object({
+							'@type': zod
+								.string()
+								.optional()
+								.describe(
+									'A URL/resource name that uniquely identifies the type of the serialized\nprotocol buffer message. This string must contain at least\none "/" character. The last segment of the URL\'s path must represent\nthe fully qualified name of the type (as in\n`path/google.protobuf.Duration`). The name should be in a canonical form\n(e.g., leading "." is not accepted).\n\nIn practice, teams usually precompile into the binary all types that they\nexpect it to use in the context of Any. However, for URLs which use the\nscheme `http`, `https`, or no scheme, one can optionally set up a type\nserver that maps type URLs to message definitions as follows:\n\n* If no scheme is provided, `https` is assumed.\n* An HTTP GET on the URL must yield a [google.protobuf.Type][]\n  value in binary format, or produce an error.\n* Applications are allowed to cache lookup results based on the\n  URL, or have them precompiled into a binary to avoid any\n  lookup. Therefore, binary compatibility needs to be preserved\n  on changes to types. (Use versioned type names to manage\n  breaking changes.)\n\nNote: this functionality is not currently available in the official\nprotobuf release, and it is not used for type URLs beginning with\ntype.googleapis.com. As of May 2023, there are no widely used type server\nimplementations and no plans to implement one.\n\nSchemes other than `http`, `https` (or the empty scheme) might be\nused with implementation specific semantics.',
+								),
+						})
+						.describe(
+							'`Any` contains an arbitrary serialized protocol buffer message along with a\nURL that describes the type of the serialized message.\n\nProtobuf library provides support to pack/unpack Any values in the form\nof utility functions or additional generated methods of the Any type.\n\nExample 1: Pack and unpack a message in C++.\n\n    Foo foo = ...;\n    Any any;\n    any.PackFrom(foo);\n    ...\n    if (any.UnpackTo(&foo)) {\n      ...\n    }\n\nExample 2: Pack and unpack a message in Java.\n\n    Foo foo = ...;\n    Any any = Any.pack(foo);\n    ...\n    if (any.is(Foo.class)) {\n      foo = any.unpack(Foo.class);\n    }\n    // or ...\n    if (any.isSameTypeAs(Foo.getDefaultInstance())) {\n      foo = any.unpack(Foo.getDefaultInstance());\n    }\n\n Example 3: Pack and unpack a message in Python.\n\n    foo = Foo(...)\n    any = Any()\n    any.Pack(foo)\n    ...\n    if any.Is(Foo.DESCRIPTOR):\n      any.Unpack(foo)\n      ...\n\n Example 4: Pack and unpack a message in Go\n\n     foo := &pb.Foo{...}\n     any, err := anypb.New(foo)\n     if err != nil {\n       ...\n     }\n     ...\n     foo := &pb.Foo{}\n     if err := any.UnmarshalTo(foo); err != nil {\n       ...\n     }\n\nThe pack methods provided by protobuf library will by default use\n\'type.googleapis.com/full.type.name\' as the type URL and the unpack\nmethods only use the fully qualified type name after the last \'/\'\nin the type URL, for example "foo.bar.com/x/y.z" will yield type\nname "y.z".\n\nJSON\n====\nThe JSON representation of an `Any` value uses the regular\nrepresentation of the deserialized, embedded message, with an\nadditional field `@type` which contains the type URL. Example:\n\n    package google.profile;\n    message Person {\n      string first_name = 1;\n      string last_name = 2;\n    }\n\n    {\n      "@type": "type.googleapis.com/google.profile.Person",\n      "firstName": <string>,\n      "lastName": <string>\n    }\n\nIf the embedded message type is well-known and has a custom JSON\nrepresentation, that representation will be embedded adding a field\n`value` which holds the custom JSON in addition to the `@type`\nfield. Example (for message [google.protobuf.Duration][]):\n\n    {\n      "@type": "type.googleapis.com/google.protobuf.Duration",\n      "value": "1.212s"\n    }',
+						),
 				)
-				.optional(),
-			message: zod.string().optional(),
+				.optional()
+				.describe(
+					'A list of messages that carry the error details.  There is a common set of\nmessage types for APIs to use.',
+				),
+			message: zod
+				.string()
+				.optional()
+				.describe(
+					'A developer-facing error message, which should be in English. Any\nuser-facing error message should be localized and sent in the\n[google.rpc.Status.details][google.rpc.Status.details] field, or localized\nby the client.',
+				),
 		})
-		.optional(),
+		.optional()
+		.describe(
+			'The `Status` type defines a logical error model that is suitable for\ndifferent programming environments, including REST APIs and RPC APIs. It is\nused by [gRPC](https://github.com/grpc). Each `Status` message contains\nthree pieces of data: error code, error message, and error details.\n\nYou can find out more about this error model and how to work with it in the\n[API Design Guide](https://cloud.google.com/apis/design/errors).',
+		),
 	result: zod
 		.object({
 			data: zod.string().optional(),

package/src/gen-wire/customer/customer.zod.ts

@@ -43,17 +43,42 @@ export const CustomerLogoutResponse = zod
 	.object({
 		cause: zod
 			.object({
-				code: zod.int().optional(),
+				code: zod
+					.int()
+					.optional()
+					.describe(
+						'The status code, which should be an enum value of\n[google.rpc.Code][google.rpc.Code].',
+					),
 				details: zod
 					.array(
-						zod.object({
-							'@type': zod.string().optional(),
-						}),
+						zod
+							.object({
+								'@type': zod
+									.string()
+									.optional()
+									.describe(
+										'A URL/resource name that uniquely identifies the type of the serialized\nprotocol buffer message. This string must contain at least\none "/" character. The last segment of the URL\'s path must represent\nthe fully qualified name of the type (as in\n`path/google.protobuf.Duration`). The name should be in a canonical form\n(e.g., leading "." is not accepted).\n\nIn practice, teams usually precompile into the binary all types that they\nexpect it to use in the context of Any. However, for URLs which use the\nscheme `http`, `https`, or no scheme, one can optionally set up a type\nserver that maps type URLs to message definitions as follows:\n\n* If no scheme is provided, `https` is assumed.\n* An HTTP GET on the URL must yield a [google.protobuf.Type][]\n  value in binary format, or produce an error.\n* Applications are allowed to cache lookup results based on the\n  URL, or have them precompiled into a binary to avoid any\n  lookup. Therefore, binary compatibility needs to be preserved\n  on changes to types. (Use versioned type names to manage\n  breaking changes.)\n\nNote: this functionality is not currently available in the official\nprotobuf release, and it is not used for type URLs beginning with\ntype.googleapis.com. As of May 2023, there are no widely used type server\nimplementations and no plans to implement one.\n\nSchemes other than `http`, `https` (or the empty scheme) might be\nused with implementation specific semantics.',
+									),
+							})
+							.describe(
+								'`Any` contains an arbitrary serialized protocol buffer message along with a\nURL that describes the type of the serialized message.\n\nProtobuf library provides support to pack/unpack Any values in the form\nof utility functions or additional generated methods of the Any type.\n\nExample 1: Pack and unpack a message in C++.\n\n    Foo foo = ...;\n    Any any;\n    any.PackFrom(foo);\n    ...\n    if (any.UnpackTo(&foo)) {\n      ...\n    }\n\nExample 2: Pack and unpack a message in Java.\n\n    Foo foo = ...;\n    Any any = Any.pack(foo);\n    ...\n    if (any.is(Foo.class)) {\n      foo = any.unpack(Foo.class);\n    }\n    // or ...\n    if (any.isSameTypeAs(Foo.getDefaultInstance())) {\n      foo = any.unpack(Foo.getDefaultInstance());\n    }\n\n Example 3: Pack and unpack a message in Python.\n\n    foo = Foo(...)\n    any = Any()\n    any.Pack(foo)\n    ...\n    if any.Is(Foo.DESCRIPTOR):\n      any.Unpack(foo)\n      ...\n\n Example 4: Pack and unpack a message in Go\n\n     foo := &pb.Foo{...}\n     any, err := anypb.New(foo)\n     if err != nil {\n       ...\n     }\n     ...\n     foo := &pb.Foo{}\n     if err := any.UnmarshalTo(foo); err != nil {\n       ...\n     }\n\nThe pack methods provided by protobuf library will by default use\n\'type.googleapis.com/full.type.name\' as the type URL and the unpack\nmethods only use the fully qualified type name after the last \'/\'\nin the type URL, for example "foo.bar.com/x/y.z" will yield type\nname "y.z".\n\nJSON\n====\nThe JSON representation of an `Any` value uses the regular\nrepresentation of the deserialized, embedded message, with an\nadditional field `@type` which contains the type URL. Example:\n\n    package google.profile;\n    message Person {\n      string first_name = 1;\n      string last_name = 2;\n    }\n\n    {\n      "@type": "type.googleapis.com/google.profile.Person",\n      "firstName": <string>,\n      "lastName": <string>\n    }\n\nIf the embedded message type is well-known and has a custom JSON\nrepresentation, that representation will be embedded adding a field\n`value` which holds the custom JSON in addition to the `@type`\nfield. Example (for message [google.protobuf.Duration][]):\n\n    {\n      "@type": "type.googleapis.com/google.protobuf.Duration",\n      "value": "1.212s"\n    }',
+							),
 					)
-					.optional(),
-				message: zod.string().optional(),
+					.optional()
+					.describe(
+						'A list of messages that carry the error details.  There is a common set of\nmessage types for APIs to use.',
+					),
+				message: zod
+					.string()
+					.optional()
+					.describe(
+						'A developer-facing error message, which should be in English. Any\nuser-facing error message should be localized and sent in the\n[google.rpc.Status.details][google.rpc.Status.details] field, or localized\nby the client.',
+					),
 			})
-			.optional(),
+			.optional()
+			.describe(
+				'The `Status` type defines a logical error model that is suitable for\ndifferent programming environments, including REST APIs and RPC APIs. It is\nused by [gRPC](https://github.com/grpc). Each `Status` message contains\nthree pieces of data: error code, error message, and error details.\n\nYou can find out more about this error model and how to work with it in the\n[API Design Guide](https://cloud.google.com/apis/design/errors).',
+			),
 	})
 	.describe(
 		'UpdateDisconnect notifies the client about\nan imminent disconnect due to specified reason.',

package/src/gen-wire/customers/customers.ts

@@ -12,7 +12,6 @@ import type {
 	ApiGetCustomerResponse,
 	ApiLicenseUsageResponse,
 	ApiLicenseUsersResponse,
-	ApiServerInfoResponse,
 	ApiUpdateCustomerResponse,
 	GetCustomer2Params,
 	GetCustomerParams,
@@ -124,11 +123,6 @@ export const // --- title start
 					},
 				});
 			};
-			const serverInfo = (
-				options?: AxiosRequestConfig,
-			): Promise<AxiosResponse<ApiServerInfoResponse>> => {
-				return axiosInstance.get(`/srvinfo`, options);
-			};
 
 			// --- footer start
 			return {
@@ -139,7 +133,6 @@ export const // --- title start
 				licenseUsage2,
 				licenseUsage3,
 				licenseUsers,
-				serverInfo,
 			};
 		};
 export type GetCustomerResult = AxiosResponse<ApiGetCustomerResponse>;
@@ -149,6 +142,5 @@ export type GetCustomer2Result = AxiosResponse<ApiGetCustomerResponse>;
 export type LicenseUsage2Result = AxiosResponse<ApiLicenseUsageResponse>;
 export type LicenseUsage3Result = AxiosResponse<ApiLicenseUsageResponse>;
 export type LicenseUsersResult = AxiosResponse<ApiLicenseUsersResponse>;
-export type ServerInfoResult = AxiosResponse<ApiServerInfoResponse>;
 
 // --- footer end

package/src/gen-wire/customers/customers.zod.ts

@@ -593,7 +593,3 @@ export const LicenseUsersResponse = zod.object({
 	next: zod.boolean().optional(),
 	page: zod.int().optional().describe('this page number !'),
 });
-
-export const ServerInfoResponse = zod.object({
-	key: zod.string().optional(),
-});

package/src/gen-wire/index.ts

@@ -889,7 +889,6 @@ export {
 	LicenseUsersParams,
 	LicenseUsersQueryParams,
 	LicenseUsersResponse,
-	ServerInfoResponse,
 	UpdateCustomerQueryParams,
 	UpdateCustomerResponse,
 } from './customers/customers.zod';
@@ -2067,12 +2066,6 @@ export {
 } from './routing-variable-service/routing-variable-service.zod';
 export * from './schema-variables-service/schema-variables-service';
 export * from './schema-variables-service/schema-variables-service.zod';
-export * from './schema-version-service/schema-version-service';
-export {
-	SearchSchemaVersionParams,
-	SearchSchemaVersionQueryParams,
-	SearchSchemaVersionResponse,
-} from './schema-version-service/schema-version-service.zod';
 export * from './services/services';
 export {
 	CreateServiceBody,
@@ -2727,6 +2720,8 @@ export {
 	ThreadManagementFlushVariablesBody,
 	ThreadManagementFlushVariablesParams,
 	ThreadManagementFlushVariablesResponse,
+	ThreadManagementGetCountersQueryParams,
+	ThreadManagementGetCountersResponse,
 	ThreadManagementGetParams,
 	ThreadManagementGetQueryParams,
 	ThreadManagementGetResponse,
@@ -2759,6 +2754,7 @@ export {
 	ThreadManagementTransferResponse,
 	threadManagementAddMemberBodyRoleDefault,
 	threadManagementAddMemberResponseMemberRoleDefault,
+	threadManagementCreateResponseThreadChannelTypeDefault,
 	threadManagementCreateResponseThreadLastMsgDeletedByRoleDefault,
 	threadManagementCreateResponseThreadLastMsgFailuresItemMemberRoleDefault,
 	threadManagementCreateResponseThreadLastMsgForwardOriginKindDefault,
@@ -2770,6 +2766,7 @@ export {
 	threadManagementCreateResponseThreadMembersItemRoleDefault,
 	threadManagementCreateResponseThreadReadStatesItemMemberRoleDefault,
 	threadManagementCreateResponseThreadTypeDefault,
+	threadManagementGetResponseChannelTypeDefault,
 	threadManagementGetResponseLastMsgDeletedByRoleDefault,
 	threadManagementGetResponseLastMsgFailuresItemMemberRoleDefault,
 	threadManagementGetResponseLastMsgForwardOriginKindDefault,
@@ -2781,6 +2778,7 @@ export {
 	threadManagementGetResponseMembersItemRoleDefault,
 	threadManagementGetResponseReadStatesItemMemberRoleDefault,
 	threadManagementGetResponseTypeDefault,
+	threadManagementSearchLeftResponseItemsItemChannelTypeDefault,
 	threadManagementSearchLeftResponseItemsItemLastMsgDeletedByRoleDefault,
 	threadManagementSearchLeftResponseItemsItemLastMsgFailuresItemMemberRoleDefault,
 	threadManagementSearchLeftResponseItemsItemLastMsgForwardOriginKindDefault,
@@ -2792,6 +2790,7 @@ export {
 	threadManagementSearchLeftResponseItemsItemMembersItemRoleDefault,
 	threadManagementSearchLeftResponseItemsItemReadStatesItemMemberRoleDefault,
 	threadManagementSearchLeftResponseItemsItemTypeDefault,
+	threadManagementSearchResponseItemsItemChannelTypeDefault,
 	threadManagementSearchResponseItemsItemLastMsgDeletedByRoleDefault,
 	threadManagementSearchResponseItemsItemLastMsgFailuresItemMemberRoleDefault,
 	threadManagementSearchResponseItemsItemLastMsgForwardOriginKindDefault,

package/src/gen-wire/index.zod.ts

@@ -95,7 +95,6 @@ export * from './routing-outbound-call-service/routing-outbound-call-service.zod
 export * from './routing-schema-service/routing-schema-service.zod';
 export * from './routing-variable-service/routing-variable-service.zod';
 export * from './schema-variables-service/schema-variables-service.zod';
-export * from './schema-version-service/schema-version-service.zod';
 export * from './services/services.zod';
 export * from './shift-template-service/shift-template-service.zod';
 export * from './skill-service/skill-service.zod';

package/src/gen-wire/list-service/list-service.zod.ts

@@ -269,17 +269,42 @@ export const CreateListCommunicationBulkResponse = zod.object({
 			zod.object({
 				error: zod
 					.object({
-						code: zod.int().optional(),
+						code: zod
+							.int()
+							.optional()
+							.describe(
+								'The status code, which should be an enum value of\n[google.rpc.Code][google.rpc.Code].',
+							),
 						details: zod
 							.array(
-								zod.object({
-									'@type': zod.string().optional(),
-								}),
+								zod
+									.object({
+										'@type': zod
+											.string()
+											.optional()
+											.describe(
+												'A URL/resource name that uniquely identifies the type of the serialized\nprotocol buffer message. This string must contain at least\none "/" character. The last segment of the URL\'s path must represent\nthe fully qualified name of the type (as in\n`path/google.protobuf.Duration`). The name should be in a canonical form\n(e.g., leading "." is not accepted).\n\nIn practice, teams usually precompile into the binary all types that they\nexpect it to use in the context of Any. However, for URLs which use the\nscheme `http`, `https`, or no scheme, one can optionally set up a type\nserver that maps type URLs to message definitions as follows:\n\n* If no scheme is provided, `https` is assumed.\n* An HTTP GET on the URL must yield a [google.protobuf.Type][]\n  value in binary format, or produce an error.\n* Applications are allowed to cache lookup results based on the\n  URL, or have them precompiled into a binary to avoid any\n  lookup. Therefore, binary compatibility needs to be preserved\n  on changes to types. (Use versioned type names to manage\n  breaking changes.)\n\nNote: this functionality is not currently available in the official\nprotobuf release, and it is not used for type URLs beginning with\ntype.googleapis.com. As of May 2023, there are no widely used type server\nimplementations and no plans to implement one.\n\nSchemes other than `http`, `https` (or the empty scheme) might be\nused with implementation specific semantics.',
+											),
+									})
+									.describe(
+										'`Any` contains an arbitrary serialized protocol buffer message along with a\nURL that describes the type of the serialized message.\n\nProtobuf library provides support to pack/unpack Any values in the form\nof utility functions or additional generated methods of the Any type.\n\nExample 1: Pack and unpack a message in C++.\n\n    Foo foo = ...;\n    Any any;\n    any.PackFrom(foo);\n    ...\n    if (any.UnpackTo(&foo)) {\n      ...\n    }\n\nExample 2: Pack and unpack a message in Java.\n\n    Foo foo = ...;\n    Any any = Any.pack(foo);\n    ...\n    if (any.is(Foo.class)) {\n      foo = any.unpack(Foo.class);\n    }\n    // or ...\n    if (any.isSameTypeAs(Foo.getDefaultInstance())) {\n      foo = any.unpack(Foo.getDefaultInstance());\n    }\n\n Example 3: Pack and unpack a message in Python.\n\n    foo = Foo(...)\n    any = Any()\n    any.Pack(foo)\n    ...\n    if any.Is(Foo.DESCRIPTOR):\n      any.Unpack(foo)\n      ...\n\n Example 4: Pack and unpack a message in Go\n\n     foo := &pb.Foo{...}\n     any, err := anypb.New(foo)\n     if err != nil {\n       ...\n     }\n     ...\n     foo := &pb.Foo{}\n     if err := any.UnmarshalTo(foo); err != nil {\n       ...\n     }\n\nThe pack methods provided by protobuf library will by default use\n\'type.googleapis.com/full.type.name\' as the type URL and the unpack\nmethods only use the fully qualified type name after the last \'/\'\nin the type URL, for example "foo.bar.com/x/y.z" will yield type\nname "y.z".\n\nJSON\n====\nThe JSON representation of an `Any` value uses the regular\nrepresentation of the deserialized, embedded message, with an\nadditional field `@type` which contains the type URL. Example:\n\n    package google.profile;\n    message Person {\n      string first_name = 1;\n      string last_name = 2;\n    }\n\n    {\n      "@type": "type.googleapis.com/google.profile.Person",\n      "firstName": <string>,\n      "lastName": <string>\n    }\n\nIf the embedded message type is well-known and has a custom JSON\nrepresentation, that representation will be embedded adding a field\n`value` which holds the custom JSON in addition to the `@type`\nfield. Example (for message [google.protobuf.Duration][]):\n\n    {\n      "@type": "type.googleapis.com/google.protobuf.Duration",\n      "value": "1.212s"\n    }',
+									),
 							)
-							.optional(),
-						message: zod.string().optional(),
+							.optional()
+							.describe(
+								'A list of messages that carry the error details.  There is a common set of\nmessage types for APIs to use.',
+							),
+						message: zod
+							.string()
+							.optional()
+							.describe(
+								'A developer-facing error message, which should be in English. Any\nuser-facing error message should be localized and sent in the\n[google.rpc.Status.details][google.rpc.Status.details] field, or localized\nby the client.',
+							),
 					})
-					.optional(),
+					.optional()
+					.describe(
+						'The `Status` type defines a logical error model that is suitable for\ndifferent programming environments, including REST APIs and RPC APIs. It is\nused by [gRPC](https://github.com/grpc). Each `Status` message contains\nthree pieces of data: error code, error message, and error details.\n\nYou can find out more about this error model and how to work with it in the\n[API Design Guide](https://cloud.google.com/apis/design/errors).',
+					),
 				index: zod.int().optional(),
 				item: zod
 					.object({

package/src/gen-wire/member-service/member-service.zod.ts

@@ -1172,17 +1172,42 @@ export const ExportMembersQueryParams = zod.object({
 export const ExportMembersResponse = zod.object({
 	error: zod
 		.object({
-			code: zod.int().optional(),
+			code: zod
+				.int()
+				.optional()
+				.describe(
+					'The status code, which should be an enum value of\n[google.rpc.Code][google.rpc.Code].',
+				),
 			details: zod
 				.array(
-					zod.object({
-						'@type': zod.string().optional(),
-					}),
+					zod
+						.object({
+							'@type': zod
+								.string()
+								.optional()
+								.describe(
+									'A URL/resource name that uniquely identifies the type of the serialized\nprotocol buffer message. This string must contain at least\none "/" character. The last segment of the URL\'s path must represent\nthe fully qualified name of the type (as in\n`path/google.protobuf.Duration`). The name should be in a canonical form\n(e.g., leading "." is not accepted).\n\nIn practice, teams usually precompile into the binary all types that they\nexpect it to use in the context of Any. However, for URLs which use the\nscheme `http`, `https`, or no scheme, one can optionally set up a type\nserver that maps type URLs to message definitions as follows:\n\n* If no scheme is provided, `https` is assumed.\n* An HTTP GET on the URL must yield a [google.protobuf.Type][]\n  value in binary format, or produce an error.\n* Applications are allowed to cache lookup results based on the\n  URL, or have them precompiled into a binary to avoid any\n  lookup. Therefore, binary compatibility needs to be preserved\n  on changes to types. (Use versioned type names to manage\n  breaking changes.)\n\nNote: this functionality is not currently available in the official\nprotobuf release, and it is not used for type URLs beginning with\ntype.googleapis.com. As of May 2023, there are no widely used type server\nimplementations and no plans to implement one.\n\nSchemes other than `http`, `https` (or the empty scheme) might be\nused with implementation specific semantics.',
+								),
+						})
+						.describe(
+							'`Any` contains an arbitrary serialized protocol buffer message along with a\nURL that describes the type of the serialized message.\n\nProtobuf library provides support to pack/unpack Any values in the form\nof utility functions or additional generated methods of the Any type.\n\nExample 1: Pack and unpack a message in C++.\n\n    Foo foo = ...;\n    Any any;\n    any.PackFrom(foo);\n    ...\n    if (any.UnpackTo(&foo)) {\n      ...\n    }\n\nExample 2: Pack and unpack a message in Java.\n\n    Foo foo = ...;\n    Any any = Any.pack(foo);\n    ...\n    if (any.is(Foo.class)) {\n      foo = any.unpack(Foo.class);\n    }\n    // or ...\n    if (any.isSameTypeAs(Foo.getDefaultInstance())) {\n      foo = any.unpack(Foo.getDefaultInstance());\n    }\n\n Example 3: Pack and unpack a message in Python.\n\n    foo = Foo(...)\n    any = Any()\n    any.Pack(foo)\n    ...\n    if any.Is(Foo.DESCRIPTOR):\n      any.Unpack(foo)\n      ...\n\n Example 4: Pack and unpack a message in Go\n\n     foo := &pb.Foo{...}\n     any, err := anypb.New(foo)\n     if err != nil {\n       ...\n     }\n     ...\n     foo := &pb.Foo{}\n     if err := any.UnmarshalTo(foo); err != nil {\n       ...\n     }\n\nThe pack methods provided by protobuf library will by default use\n\'type.googleapis.com/full.type.name\' as the type URL and the unpack\nmethods only use the fully qualified type name after the last \'/\'\nin the type URL, for example "foo.bar.com/x/y.z" will yield type\nname "y.z".\n\nJSON\n====\nThe JSON representation of an `Any` value uses the regular\nrepresentation of the deserialized, embedded message, with an\nadditional field `@type` which contains the type URL. Example:\n\n    package google.profile;\n    message Person {\n      string first_name = 1;\n      string last_name = 2;\n    }\n\n    {\n      "@type": "type.googleapis.com/google.profile.Person",\n      "firstName": <string>,\n      "lastName": <string>\n    }\n\nIf the embedded message type is well-known and has a custom JSON\nrepresentation, that representation will be embedded adding a field\n`value` which holds the custom JSON in addition to the `@type`\nfield. Example (for message [google.protobuf.Duration][]):\n\n    {\n      "@type": "type.googleapis.com/google.protobuf.Duration",\n      "value": "1.212s"\n    }',
+						),
 				)
-				.optional(),
-			message: zod.string().optional(),
+				.optional()
+				.describe(
+					'A list of messages that carry the error details.  There is a common set of\nmessage types for APIs to use.',
+				),
+			message: zod
+				.string()
+				.optional()
+				.describe(
+					'A developer-facing error message, which should be in English. Any\nuser-facing error message should be localized and sent in the\n[google.rpc.Status.details][google.rpc.Status.details] field, or localized\nby the client.',
+				),
 		})
-		.optional(),
+		.optional()
+		.describe(
+			'The `Status` type defines a logical error model that is suitable for\ndifferent programming environments, including REST APIs and RPC APIs. It is\nused by [gRPC](https://github.com/grpc). Each `Status` message contains\nthree pieces of data: error code, error message, and error details.\n\nYou can find out more about this error model and how to work with it in the\n[API Design Guide](https://cloud.google.com/apis/design/errors).',
+		),
 	result: zod
 		.object({
 			data: zod.string().optional(),

package/src/gen-wire/messages/messages.zod.ts

@@ -64,17 +64,42 @@ export const MessagesServiceBroadcastMessageResponse = zod.object({
 			zod.object({
 				error: zod
 					.object({
-						code: zod.int().optional(),
+						code: zod
+							.int()
+							.optional()
+							.describe(
+								'The status code, which should be an enum value of\n[google.rpc.Code][google.rpc.Code].',
+							),
 						details: zod
 							.array(
-								zod.object({
-									'@type': zod.string().optional(),
-								}),
+								zod
+									.object({
+										'@type': zod
+											.string()
+											.optional()
+											.describe(
+												'A URL/resource name that uniquely identifies the type of the serialized\nprotocol buffer message. This string must contain at least\none "/" character. The last segment of the URL\'s path must represent\nthe fully qualified name of the type (as in\n`path/google.protobuf.Duration`). The name should be in a canonical form\n(e.g., leading "." is not accepted).\n\nIn practice, teams usually precompile into the binary all types that they\nexpect it to use in the context of Any. However, for URLs which use the\nscheme `http`, `https`, or no scheme, one can optionally set up a type\nserver that maps type URLs to message definitions as follows:\n\n* If no scheme is provided, `https` is assumed.\n* An HTTP GET on the URL must yield a [google.protobuf.Type][]\n  value in binary format, or produce an error.\n* Applications are allowed to cache lookup results based on the\n  URL, or have them precompiled into a binary to avoid any\n  lookup. Therefore, binary compatibility needs to be preserved\n  on changes to types. (Use versioned type names to manage\n  breaking changes.)\n\nNote: this functionality is not currently available in the official\nprotobuf release, and it is not used for type URLs beginning with\ntype.googleapis.com. As of May 2023, there are no widely used type server\nimplementations and no plans to implement one.\n\nSchemes other than `http`, `https` (or the empty scheme) might be\nused with implementation specific semantics.',
+											),
+									})
+									.describe(
+										'`Any` contains an arbitrary serialized protocol buffer message along with a\nURL that describes the type of the serialized message.\n\nProtobuf library provides support to pack/unpack Any values in the form\nof utility functions or additional generated methods of the Any type.\n\nExample 1: Pack and unpack a message in C++.\n\n    Foo foo = ...;\n    Any any;\n    any.PackFrom(foo);\n    ...\n    if (any.UnpackTo(&foo)) {\n      ...\n    }\n\nExample 2: Pack and unpack a message in Java.\n\n    Foo foo = ...;\n    Any any = Any.pack(foo);\n    ...\n    if (any.is(Foo.class)) {\n      foo = any.unpack(Foo.class);\n    }\n    // or ...\n    if (any.isSameTypeAs(Foo.getDefaultInstance())) {\n      foo = any.unpack(Foo.getDefaultInstance());\n    }\n\n Example 3: Pack and unpack a message in Python.\n\n    foo = Foo(...)\n    any = Any()\n    any.Pack(foo)\n    ...\n    if any.Is(Foo.DESCRIPTOR):\n      any.Unpack(foo)\n      ...\n\n Example 4: Pack and unpack a message in Go\n\n     foo := &pb.Foo{...}\n     any, err := anypb.New(foo)\n     if err != nil {\n       ...\n     }\n     ...\n     foo := &pb.Foo{}\n     if err := any.UnmarshalTo(foo); err != nil {\n       ...\n     }\n\nThe pack methods provided by protobuf library will by default use\n\'type.googleapis.com/full.type.name\' as the type URL and the unpack\nmethods only use the fully qualified type name after the last \'/\'\nin the type URL, for example "foo.bar.com/x/y.z" will yield type\nname "y.z".\n\nJSON\n====\nThe JSON representation of an `Any` value uses the regular\nrepresentation of the deserialized, embedded message, with an\nadditional field `@type` which contains the type URL. Example:\n\n    package google.profile;\n    message Person {\n      string first_name = 1;\n      string last_name = 2;\n    }\n\n    {\n      "@type": "type.googleapis.com/google.profile.Person",\n      "firstName": <string>,\n      "lastName": <string>\n    }\n\nIf the embedded message type is well-known and has a custom JSON\nrepresentation, that representation will be embedded adding a field\n`value` which holds the custom JSON in addition to the `@type`\nfield. Example (for message [google.protobuf.Duration][]):\n\n    {\n      "@type": "type.googleapis.com/google.protobuf.Duration",\n      "value": "1.212s"\n    }',
+									),
 							)
-							.optional(),
-						message: zod.string().optional(),
+							.optional()
+							.describe(
+								'A list of messages that carry the error details.  There is a common set of\nmessage types for APIs to use.',
+							),
+						message: zod
+							.string()
+							.optional()
+							.describe(
+								'A developer-facing error message, which should be in English. Any\nuser-facing error message should be localized and sent in the\n[google.rpc.Status.details][google.rpc.Status.details] field, or localized\nby the client.',
+							),
 					})
-					.optional(),
+					.optional()
+					.describe(
+						'The `Status` type defines a logical error model that is suitable for\ndifferent programming environments, including REST APIs and RPC APIs. It is\nused by [gRPC](https://github.com/grpc). Each `Status` message contains\nthree pieces of data: error code, error message, and error details.\n\nYou can find out more about this error model and how to work with it in the\n[API Design Guide](https://cloud.google.com/apis/design/errors).',
+					),
 				peer_id: zod.string().optional(),
 			}),
 		)

package/src/gen-wire/pdf-service/pdf-service.zod.ts

@@ -32,17 +32,42 @@ export const DownloadScreenrecordingArchiveQueryParams = zod.object({
 export const DownloadScreenrecordingArchiveResponse = zod.object({
 	error: zod
 		.object({
-			code: zod.int().optional(),
+			code: zod
+				.int()
+				.optional()
+				.describe(
+					'The status code, which should be an enum value of\n[google.rpc.Code][google.rpc.Code].',
+				),
 			details: zod
 				.array(
-					zod.object({
-						'@type': zod.string().optional(),
-					}),
+					zod
+						.object({
+							'@type': zod
+								.string()
+								.optional()
+								.describe(
+									'A URL/resource name that uniquely identifies the type of the serialized\nprotocol buffer message. This string must contain at least\none "/" character. The last segment of the URL\'s path must represent\nthe fully qualified name of the type (as in\n`path/google.protobuf.Duration`). The name should be in a canonical form\n(e.g., leading "." is not accepted).\n\nIn practice, teams usually precompile into the binary all types that they\nexpect it to use in the context of Any. However, for URLs which use the\nscheme `http`, `https`, or no scheme, one can optionally set up a type\nserver that maps type URLs to message definitions as follows:\n\n* If no scheme is provided, `https` is assumed.\n* An HTTP GET on the URL must yield a [google.protobuf.Type][]\n  value in binary format, or produce an error.\n* Applications are allowed to cache lookup results based on the\n  URL, or have them precompiled into a binary to avoid any\n  lookup. Therefore, binary compatibility needs to be preserved\n  on changes to types. (Use versioned type names to manage\n  breaking changes.)\n\nNote: this functionality is not currently available in the official\nprotobuf release, and it is not used for type URLs beginning with\ntype.googleapis.com. As of May 2023, there are no widely used type server\nimplementations and no plans to implement one.\n\nSchemes other than `http`, `https` (or the empty scheme) might be\nused with implementation specific semantics.',
+								),
+						})
+						.describe(
+							'`Any` contains an arbitrary serialized protocol buffer message along with a\nURL that describes the type of the serialized message.\n\nProtobuf library provides support to pack/unpack Any values in the form\nof utility functions or additional generated methods of the Any type.\n\nExample 1: Pack and unpack a message in C++.\n\n    Foo foo = ...;\n    Any any;\n    any.PackFrom(foo);\n    ...\n    if (any.UnpackTo(&foo)) {\n      ...\n    }\n\nExample 2: Pack and unpack a message in Java.\n\n    Foo foo = ...;\n    Any any = Any.pack(foo);\n    ...\n    if (any.is(Foo.class)) {\n      foo = any.unpack(Foo.class);\n    }\n    // or ...\n    if (any.isSameTypeAs(Foo.getDefaultInstance())) {\n      foo = any.unpack(Foo.getDefaultInstance());\n    }\n\n Example 3: Pack and unpack a message in Python.\n\n    foo = Foo(...)\n    any = Any()\n    any.Pack(foo)\n    ...\n    if any.Is(Foo.DESCRIPTOR):\n      any.Unpack(foo)\n      ...\n\n Example 4: Pack and unpack a message in Go\n\n     foo := &pb.Foo{...}\n     any, err := anypb.New(foo)\n     if err != nil {\n       ...\n     }\n     ...\n     foo := &pb.Foo{}\n     if err := any.UnmarshalTo(foo); err != nil {\n       ...\n     }\n\nThe pack methods provided by protobuf library will by default use\n\'type.googleapis.com/full.type.name\' as the type URL and the unpack\nmethods only use the fully qualified type name after the last \'/\'\nin the type URL, for example "foo.bar.com/x/y.z" will yield type\nname "y.z".\n\nJSON\n====\nThe JSON representation of an `Any` value uses the regular\nrepresentation of the deserialized, embedded message, with an\nadditional field `@type` which contains the type URL. Example:\n\n    package google.profile;\n    message Person {\n      string first_name = 1;\n      string last_name = 2;\n    }\n\n    {\n      "@type": "type.googleapis.com/google.profile.Person",\n      "firstName": <string>,\n      "lastName": <string>\n    }\n\nIf the embedded message type is well-known and has a custom JSON\nrepresentation, that representation will be embedded adding a field\n`value` which holds the custom JSON in addition to the `@type`\nfield. Example (for message [google.protobuf.Duration][]):\n\n    {\n      "@type": "type.googleapis.com/google.protobuf.Duration",\n      "value": "1.212s"\n    }',
+						),
 				)
-				.optional(),
-			message: zod.string().optional(),
+				.optional()
+				.describe(
+					'A list of messages that carry the error details.  There is a common set of\nmessage types for APIs to use.',
+				),
+			message: zod
+				.string()
+				.optional()
+				.describe(
+					'A developer-facing error message, which should be in English. Any\nuser-facing error message should be localized and sent in the\n[google.rpc.Status.details][google.rpc.Status.details] field, or localized\nby the client.',
+				),
 		})
-		.optional(),
+		.optional()
+		.describe(
+			'The `Status` type defines a logical error model that is suitable for\ndifferent programming environments, including REST APIs and RPC APIs. It is\nused by [gRPC](https://github.com/grpc). Each `Status` message contains\nthree pieces of data: error code, error message, and error details.\n\nYou can find out more about this error model and how to work with it in the\n[API Design Guide](https://cloud.google.com/apis/design/errors).',
+		),
 	result: zod
 		.object({
 			data: zod.string().optional(),
@@ -79,17 +104,42 @@ export const DownloadScreenshotArchiveQueryParams = zod.object({
 export const DownloadScreenshotArchiveResponse = zod.object({
 	error: zod
 		.object({
-			code: zod.int().optional(),
+			code: zod
+				.int()
+				.optional()
+				.describe(
+					'The status code, which should be an enum value of\n[google.rpc.Code][google.rpc.Code].',
+				),
 			details: zod
 				.array(
-					zod.object({
-						'@type': zod.string().optional(),
-					}),
+					zod
+						.object({
+							'@type': zod
+								.string()
+								.optional()
+								.describe(
+									'A URL/resource name that uniquely identifies the type of the serialized\nprotocol buffer message. This string must contain at least\none "/" character. The last segment of the URL\'s path must represent\nthe fully qualified name of the type (as in\n`path/google.protobuf.Duration`). The name should be in a canonical form\n(e.g., leading "." is not accepted).\n\nIn practice, teams usually precompile into the binary all types that they\nexpect it to use in the context of Any. However, for URLs which use the\nscheme `http`, `https`, or no scheme, one can optionally set up a type\nserver that maps type URLs to message definitions as follows:\n\n* If no scheme is provided, `https` is assumed.\n* An HTTP GET on the URL must yield a [google.protobuf.Type][]\n  value in binary format, or produce an error.\n* Applications are allowed to cache lookup results based on the\n  URL, or have them precompiled into a binary to avoid any\n  lookup. Therefore, binary compatibility needs to be preserved\n  on changes to types. (Use versioned type names to manage\n  breaking changes.)\n\nNote: this functionality is not currently available in the official\nprotobuf release, and it is not used for type URLs beginning with\ntype.googleapis.com. As of May 2023, there are no widely used type server\nimplementations and no plans to implement one.\n\nSchemes other than `http`, `https` (or the empty scheme) might be\nused with implementation specific semantics.',
+								),
+						})
+						.describe(
+							'`Any` contains an arbitrary serialized protocol buffer message along with a\nURL that describes the type of the serialized message.\n\nProtobuf library provides support to pack/unpack Any values in the form\nof utility functions or additional generated methods of the Any type.\n\nExample 1: Pack and unpack a message in C++.\n\n    Foo foo = ...;\n    Any any;\n    any.PackFrom(foo);\n    ...\n    if (any.UnpackTo(&foo)) {\n      ...\n    }\n\nExample 2: Pack and unpack a message in Java.\n\n    Foo foo = ...;\n    Any any = Any.pack(foo);\n    ...\n    if (any.is(Foo.class)) {\n      foo = any.unpack(Foo.class);\n    }\n    // or ...\n    if (any.isSameTypeAs(Foo.getDefaultInstance())) {\n      foo = any.unpack(Foo.getDefaultInstance());\n    }\n\n Example 3: Pack and unpack a message in Python.\n\n    foo = Foo(...)\n    any = Any()\n    any.Pack(foo)\n    ...\n    if any.Is(Foo.DESCRIPTOR):\n      any.Unpack(foo)\n      ...\n\n Example 4: Pack and unpack a message in Go\n\n     foo := &pb.Foo{...}\n     any, err := anypb.New(foo)\n     if err != nil {\n       ...\n     }\n     ...\n     foo := &pb.Foo{}\n     if err := any.UnmarshalTo(foo); err != nil {\n       ...\n     }\n\nThe pack methods provided by protobuf library will by default use\n\'type.googleapis.com/full.type.name\' as the type URL and the unpack\nmethods only use the fully qualified type name after the last \'/\'\nin the type URL, for example "foo.bar.com/x/y.z" will yield type\nname "y.z".\n\nJSON\n====\nThe JSON representation of an `Any` value uses the regular\nrepresentation of the deserialized, embedded message, with an\nadditional field `@type` which contains the type URL. Example:\n\n    package google.profile;\n    message Person {\n      string first_name = 1;\n      string last_name = 2;\n    }\n\n    {\n      "@type": "type.googleapis.com/google.profile.Person",\n      "firstName": <string>,\n      "lastName": <string>\n    }\n\nIf the embedded message type is well-known and has a custom JSON\nrepresentation, that representation will be embedded adding a field\n`value` which holds the custom JSON in addition to the `@type`\nfield. Example (for message [google.protobuf.Duration][]):\n\n    {\n      "@type": "type.googleapis.com/google.protobuf.Duration",\n      "value": "1.212s"\n    }',
+						),
 				)
-				.optional(),
-			message: zod.string().optional(),
+				.optional()
+				.describe(
+					'A list of messages that carry the error details.  There is a common set of\nmessage types for APIs to use.',
+				),
+			message: zod
+				.string()
+				.optional()
+				.describe(
+					'A developer-facing error message, which should be in English. Any\nuser-facing error message should be localized and sent in the\n[google.rpc.Status.details][google.rpc.Status.details] field, or localized\nby the client.',
+				),
 		})
-		.optional(),
+		.optional()
+		.describe(
+			'The `Status` type defines a logical error model that is suitable for\ndifferent programming environments, including REST APIs and RPC APIs. It is\nused by [gRPC](https://github.com/grpc). Each `Status` message contains\nthree pieces of data: error code, error message, and error details.\n\nYou can find out more about this error model and how to work with it in the\n[API Design Guide](https://cloud.google.com/apis/design/errors).',
+		),
 	result: zod
 		.object({
 			data: zod.string().optional(),
@@ -258,17 +308,42 @@ export const DownloadCallArchiveQueryParams = zod.object({
 export const DownloadCallArchiveResponse = zod.object({
 	error: zod
 		.object({
-			code: zod.int().optional(),
+			code: zod
+				.int()
+				.optional()
+				.describe(
+					'The status code, which should be an enum value of\n[google.rpc.Code][google.rpc.Code].',
+				),
 			details: zod
 				.array(
-					zod.object({
-						'@type': zod.string().optional(),
-					}),
+					zod
+						.object({
+							'@type': zod
+								.string()
+								.optional()
+								.describe(
+									'A URL/resource name that uniquely identifies the type of the serialized\nprotocol buffer message. This string must contain at least\none "/" character. The last segment of the URL\'s path must represent\nthe fully qualified name of the type (as in\n`path/google.protobuf.Duration`). The name should be in a canonical form\n(e.g., leading "." is not accepted).\n\nIn practice, teams usually precompile into the binary all types that they\nexpect it to use in the context of Any. However, for URLs which use the\nscheme `http`, `https`, or no scheme, one can optionally set up a type\nserver that maps type URLs to message definitions as follows:\n\n* If no scheme is provided, `https` is assumed.\n* An HTTP GET on the URL must yield a [google.protobuf.Type][]\n  value in binary format, or produce an error.\n* Applications are allowed to cache lookup results based on the\n  URL, or have them precompiled into a binary to avoid any\n  lookup. Therefore, binary compatibility needs to be preserved\n  on changes to types. (Use versioned type names to manage\n  breaking changes.)\n\nNote: this functionality is not currently available in the official\nprotobuf release, and it is not used for type URLs beginning with\ntype.googleapis.com. As of May 2023, there are no widely used type server\nimplementations and no plans to implement one.\n\nSchemes other than `http`, `https` (or the empty scheme) might be\nused with implementation specific semantics.',
+								),
+						})
+						.describe(
+							'`Any` contains an arbitrary serialized protocol buffer message along with a\nURL that describes the type of the serialized message.\n\nProtobuf library provides support to pack/unpack Any values in the form\nof utility functions or additional generated methods of the Any type.\n\nExample 1: Pack and unpack a message in C++.\n\n    Foo foo = ...;\n    Any any;\n    any.PackFrom(foo);\n    ...\n    if (any.UnpackTo(&foo)) {\n      ...\n    }\n\nExample 2: Pack and unpack a message in Java.\n\n    Foo foo = ...;\n    Any any = Any.pack(foo);\n    ...\n    if (any.is(Foo.class)) {\n      foo = any.unpack(Foo.class);\n    }\n    // or ...\n    if (any.isSameTypeAs(Foo.getDefaultInstance())) {\n      foo = any.unpack(Foo.getDefaultInstance());\n    }\n\n Example 3: Pack and unpack a message in Python.\n\n    foo = Foo(...)\n    any = Any()\n    any.Pack(foo)\n    ...\n    if any.Is(Foo.DESCRIPTOR):\n      any.Unpack(foo)\n      ...\n\n Example 4: Pack and unpack a message in Go\n\n     foo := &pb.Foo{...}\n     any, err := anypb.New(foo)\n     if err != nil {\n       ...\n     }\n     ...\n     foo := &pb.Foo{}\n     if err := any.UnmarshalTo(foo); err != nil {\n       ...\n     }\n\nThe pack methods provided by protobuf library will by default use\n\'type.googleapis.com/full.type.name\' as the type URL and the unpack\nmethods only use the fully qualified type name after the last \'/\'\nin the type URL, for example "foo.bar.com/x/y.z" will yield type\nname "y.z".\n\nJSON\n====\nThe JSON representation of an `Any` value uses the regular\nrepresentation of the deserialized, embedded message, with an\nadditional field `@type` which contains the type URL. Example:\n\n    package google.profile;\n    message Person {\n      string first_name = 1;\n      string last_name = 2;\n    }\n\n    {\n      "@type": "type.googleapis.com/google.profile.Person",\n      "firstName": <string>,\n      "lastName": <string>\n    }\n\nIf the embedded message type is well-known and has a custom JSON\nrepresentation, that representation will be embedded adding a field\n`value` which holds the custom JSON in addition to the `@type`\nfield. Example (for message [google.protobuf.Duration][]):\n\n    {\n      "@type": "type.googleapis.com/google.protobuf.Duration",\n      "value": "1.212s"\n    }',
+						),
 				)
-				.optional(),
-			message: zod.string().optional(),
+				.optional()
+				.describe(
+					'A list of messages that carry the error details.  There is a common set of\nmessage types for APIs to use.',
+				),
+			message: zod
+				.string()
+				.optional()
+				.describe(
+					'A developer-facing error message, which should be in English. Any\nuser-facing error message should be localized and sent in the\n[google.rpc.Status.details][google.rpc.Status.details] field, or localized\nby the client.',
+				),
 		})
-		.optional(),
+		.optional()
+		.describe(
+			'The `Status` type defines a logical error model that is suitable for\ndifferent programming environments, including REST APIs and RPC APIs. It is\nused by [gRPC](https://github.com/grpc). Each `Status` message contains\nthree pieces of data: error code, error message, and error details.\n\nYou can find out more about this error model and how to work with it in the\n[API Design Guide](https://cloud.google.com/apis/design/errors).',
+		),
 	result: zod
 		.object({
 			data: zod.string().optional(),
@@ -302,17 +377,42 @@ export const DownloadCallScreenrecordingArchiveQueryParams = zod.object({
 export const DownloadCallScreenrecordingArchiveResponse = zod.object({
 	error: zod
 		.object({
-			code: zod.int().optional(),
+			code: zod
+				.int()
+				.optional()
+				.describe(
+					'The status code, which should be an enum value of\n[google.rpc.Code][google.rpc.Code].',
+				),
 			details: zod
 				.array(
-					zod.object({
-						'@type': zod.string().optional(),
-					}),
+					zod
+						.object({
+							'@type': zod
+								.string()
+								.optional()
+								.describe(
+									'A URL/resource name that uniquely identifies the type of the serialized\nprotocol buffer message. This string must contain at least\none "/" character. The last segment of the URL\'s path must represent\nthe fully qualified name of the type (as in\n`path/google.protobuf.Duration`). The name should be in a canonical form\n(e.g., leading "." is not accepted).\n\nIn practice, teams usually precompile into the binary all types that they\nexpect it to use in the context of Any. However, for URLs which use the\nscheme `http`, `https`, or no scheme, one can optionally set up a type\nserver that maps type URLs to message definitions as follows:\n\n* If no scheme is provided, `https` is assumed.\n* An HTTP GET on the URL must yield a [google.protobuf.Type][]\n  value in binary format, or produce an error.\n* Applications are allowed to cache lookup results based on the\n  URL, or have them precompiled into a binary to avoid any\n  lookup. Therefore, binary compatibility needs to be preserved\n  on changes to types. (Use versioned type names to manage\n  breaking changes.)\n\nNote: this functionality is not currently available in the official\nprotobuf release, and it is not used for type URLs beginning with\ntype.googleapis.com. As of May 2023, there are no widely used type server\nimplementations and no plans to implement one.\n\nSchemes other than `http`, `https` (or the empty scheme) might be\nused with implementation specific semantics.',
+								),
+						})
+						.describe(
+							'`Any` contains an arbitrary serialized protocol buffer message along with a\nURL that describes the type of the serialized message.\n\nProtobuf library provides support to pack/unpack Any values in the form\nof utility functions or additional generated methods of the Any type.\n\nExample 1: Pack and unpack a message in C++.\n\n    Foo foo = ...;\n    Any any;\n    any.PackFrom(foo);\n    ...\n    if (any.UnpackTo(&foo)) {\n      ...\n    }\n\nExample 2: Pack and unpack a message in Java.\n\n    Foo foo = ...;\n    Any any = Any.pack(foo);\n    ...\n    if (any.is(Foo.class)) {\n      foo = any.unpack(Foo.class);\n    }\n    // or ...\n    if (any.isSameTypeAs(Foo.getDefaultInstance())) {\n      foo = any.unpack(Foo.getDefaultInstance());\n    }\n\n Example 3: Pack and unpack a message in Python.\n\n    foo = Foo(...)\n    any = Any()\n    any.Pack(foo)\n    ...\n    if any.Is(Foo.DESCRIPTOR):\n      any.Unpack(foo)\n      ...\n\n Example 4: Pack and unpack a message in Go\n\n     foo := &pb.Foo{...}\n     any, err := anypb.New(foo)\n     if err != nil {\n       ...\n     }\n     ...\n     foo := &pb.Foo{}\n     if err := any.UnmarshalTo(foo); err != nil {\n       ...\n     }\n\nThe pack methods provided by protobuf library will by default use\n\'type.googleapis.com/full.type.name\' as the type URL and the unpack\nmethods only use the fully qualified type name after the last \'/\'\nin the type URL, for example "foo.bar.com/x/y.z" will yield type\nname "y.z".\n\nJSON\n====\nThe JSON representation of an `Any` value uses the regular\nrepresentation of the deserialized, embedded message, with an\nadditional field `@type` which contains the type URL. Example:\n\n    package google.profile;\n    message Person {\n      string first_name = 1;\n      string last_name = 2;\n    }\n\n    {\n      "@type": "type.googleapis.com/google.profile.Person",\n      "firstName": <string>,\n      "lastName": <string>\n    }\n\nIf the embedded message type is well-known and has a custom JSON\nrepresentation, that representation will be embedded adding a field\n`value` which holds the custom JSON in addition to the `@type`\nfield. Example (for message [google.protobuf.Duration][]):\n\n    {\n      "@type": "type.googleapis.com/google.protobuf.Duration",\n      "value": "1.212s"\n    }',
+						),
 				)
-				.optional(),
-			message: zod.string().optional(),
+				.optional()
+				.describe(
+					'A list of messages that carry the error details.  There is a common set of\nmessage types for APIs to use.',
+				),
+			message: zod
+				.string()
+				.optional()
+				.describe(
+					'A developer-facing error message, which should be in English. Any\nuser-facing error message should be localized and sent in the\n[google.rpc.Status.details][google.rpc.Status.details] field, or localized\nby the client.',
+				),
 		})
-		.optional(),
+		.optional()
+		.describe(
+			'The `Status` type defines a logical error model that is suitable for\ndifferent programming environments, including REST APIs and RPC APIs. It is\nused by [gRPC](https://github.com/grpc). Each `Status` message contains\nthree pieces of data: error code, error message, and error details.\n\nYou can find out more about this error model and how to work with it in the\n[API Design Guide](https://cloud.google.com/apis/design/errors).',
+		),
 	result: zod
 		.object({
 			data: zod.string().optional(),