This issue collects various ideas for improvements (following completion of gh-4148) around named (as opposed to positional) task arguments.

• raise an error when extra strings are provided to an Alias task (see point 3 of Allow named args in depends-on #3536 (comment))
• allow adding named args in depends-on via pixi task add ... (see also feat(tasks): enhance pixi task add #3884, Improve pixi task add CLI command. #3828)
• add description field to args (Allow named args in depends-on #3536 (comment))
• allow specifying named args during pixi run, something like pixi run my-task --my-arg-3=foo --my-arg-1=bar
• figure out how to run a dependency task as --frozen
• allow templating in the name of dependent tasks (Could the depends-on -> list -> { task = "{{ a_task_name }}", ... } be supported? #4042)

This last point in particular would need a lot of thought. We need to be careful about flags getting consumed by pixi run instead of as args to the task.