Given the other comments, it seems to me that Pod::Usage could spot this case and give a more useful error message. It may be worth filing a feature request via the module's github with a reference back to this thread.