BTW, I was not asked by my manager to do this. I just saw a need for something like this and hoping to just do it myself for extra points :-)

Why do you really want to do this? Is it really to impress your management and get "extra points?" You say you saw a need but whose need is it? After you put the effort into this and your tool is created, is it going to be used, or most of the team already familiar the tools that exist?

How are the tools used? If they are like most Unix tools, they can probably be used in chains of filters where the output of one script is used as the input to another. Will your wrapper support this? How will your wrapper handle command line arguments with more than simple logic? (I.e. this switch makes sense only when used in conjunction with this other one or similar.)

Could a better solution be writing some documentation?

If I was your manager and I saw you take the initiative to write some documentation for our in-house tools, I'd be impressed. ;-) I'd be less impressed by a gui front-end to command line tools though.

-sauoq
"My two cents aren't worth a dime.";