The problem is that authors use boilerplates. With Module::Starter there are lots of modules with abstracts "The great new [modulename]". No matter what wiz-bang new module starter system somebody comes up with, there will be some kind of boilerplate text. Unless maybe it asks you to write the documentation before you write the module. (Fine for some developers, but not everyone.)
I do think this is appropriate for something that Module::Build to use before building distributions. This is the most natural place for such tests, and if it's run as part of the "Build dist" process, then one doesn't need to worry about forgetting to run it.
Of course there should be options to override it (either by explicitly telling it to ignore files or setting some option to disable it).
The purpose of it isn't to stop the author from building a distribution, but to warn the author before uploading it.
If the utility is used by PAUSE or CPANTS, that might be good too.
