Why not have all arguments named, for clarity and flexibility?

[ajmetz]

It's conventional within eprints to have a few values after a command that are arguments,
and then options such as --verbose too. With users typically reading the documentation to understand what order arguments are expected to be given in.

Because ChangeName builds on this with string options - for example the language option, which is essentially a named argument, it makes sense to have all arguments named doesn't it? Then you never have to remember what order they are expected, nor keep looking it up in the documentation.
I also read somewhere it's good practice to name all your arguments.

Of course, the ultimate in user friendliness is likely to be moving functionality from the commandline to the web gui. Presently, there is of course the Batch Edit tool in the web gui: https://github.com/eprintsug/batchedit-extended