How to make sub-command descriptions in task summary more useful?

[vctls]

I use {{.CLI_ARGS}} and other variables a lot in order to compose tasks while retaining the ability to run parent tasks with custom arguments.
Sometimes a task will call another task multiple times with different variables. I use for loops now and then too.
But when displaying the summary, the variables are not shown in the commands list. For example:

vars:
  DATABASES: main job_processing key_value_store authn
tasks:
  db.dump:
    desc: "Dump the databases to a set of SQL files."
    summary: |-
      Dump the databases to a set of SQL files.
      Use the variable NAME to prefix the dump filenames.
    cmds:
      - for: { var: DATABASES }
        task: db.pg_dump
        vars:
          DB: '{{.ITEM}}'
          # language=sh
          FILE: '> .tmp/{{.NAME | default "db_dump" }}.{{.ITEM}}.sql'

results in

❯ task --summary db.dump
task: db.dump

Dump the databases to a set of SQL files.
Use the variable NAME to prefix the dump filenames.

commands:
 - Task: db.pg_dump
 - Task: db.pg_dump
 - Task: db.pg_dump
 - Task: db.pg_dump

Knowing that this tasks call the tasks for pg_dump four times is not very useful.
Am I composing my tasks wrong?
Or should there be some way of printing more context about the commands being called?

[pd93]

This is an interesting (and unintended) side-effect of the way that for loops were implemented. Your example is functionally identical to writing out the task in YAML 4 times with different variables. Hence the (admittedly unhelpful) output. Could you provide an example of what information you'd like to see instead? An example of how you'd expect the output to look would help to feed this discussion.

[vctls]

I'm not sure, really.
To be honest, I could do without the automatic sub-commands description.
So either not showing them at all and only using the content of the summary property,
or printing the list of commands along with the interpolated values of each variable. Not sure about the format, either.
Maybe something like - Task: DB='main' FILE='> .tmp/custom_name.main.sql' db.pg_dump
Or on multiple lines?

- Task: db.pg_dump
  vars: DB='main' FILE='> .tmp/custom_name.main.sql'
- Task: db.pg_dump
...

Or maybe using the other format? - Task: db.pg_dump "DB=main" "FILE=> .tmp/custom_name.main.sql"
This would be nice if one were to copy-paste the task to run it independently.
(oof, that => is confusing though)