Union type descriptions prints as JSON when using zod

When defining inputs with union type, I've noticed that using z from the trpc-cli causes that CLI to print JSON-like type description (e.g. Any of: [{"type":"string"},{"type":"boolean"}] (default: false)), whereas using z from zod package produces much clearer, human-readable output (e.g. type: string or boolean (default: false)).

Using z from trpc-cli:

import { z } from "trpc-cli";

import { t } from "~/trpc";

export const init = t.procedure
  .input(
    z.object({
      type: z.string().or(z.boolean()),
    }),
  )
  .mutation(({ input }) => {
    console.log(input);
  });

Usage: index init [options]

Options:
  --type [value]   Any of: [{"type":"string"},{"type":"boolean"}] (default: false)
  -h, --help       display help for command

Using z from zod:

import { z } from "zod";

import { t } from "~/trpc";

export const init = t.procedure
  .input(
    z.object({
      type: z.string().or(z.boolean()),
    }),
  )
  .mutation(({ input }) => {
    console.log(input);
  });

Usage: index init [options]

Options:
  --type [value]   type: string or boolean (default: false)
  -h, --help       display help for command

Start by reproducing the CLI help output for a tRPC input using z.string().or(z.boolean()), comparing z from trpc-cli with z from zod. Trace the union type description path and verify that the resulting option text is human-readable rather than JSON-like, while preserving the default value.