The CPAN library contains, at this writing, “186,946 modules.”   Unsurprisingly, a great many of them are redundant.   Anyone can contribute one, and I am quite sure that many of them arrive in the library more-or-less as yours might:   “I wrote this, I thought it was cool, and I wanted to share it.”   Thank you.

But you want your contribution, of course, to actually be used.   (At one time it was estimated that over 60% of the apps in Apple’s on-line store had never been downloaded ... at all.)   You want your contribution to be memorable.   To do that, first it must be found.   I literally have to stumble upon your module to know that it exists, and to know that it is right for me.   It will attract my second-glance if it does one or two things “thoroughly,” and if these things that it does are not entirely trivial.   But it all starts with the module name, and the words that you use to describe it.   Util::Number is as non-descriptive as it gets.   Phrases like “pretty” also convey no sense of “what you mean by that.”   Say exactly what your module does, and, in the synopsis, give a short but descriptive example.   If there is a particular word or phrase that I might distinctly be searching-for in order to separate the wheat from the chaff in my search, use that word or phrase.

I will take at least a passing glance at the source-code.   Make it neat and tidy.   Make sure that I can see it all, on the CPAN site, without downloading it.

Your module does not have to be a Swiss Army® knife, full of both source-code and dependencies, to be successful.   There is plenty of room for a good pocketknife or even a good bottle-opener.   It simply won’t be the only, nor the first, module that does more-or-less the same thing. But it must be thoroughly implemented, non-trivial (“It is to my advantage to download something to do this, rather than do it myself”), very well-tested (that is to say, good pre-installation online test suite), and well-named and described.