I agree. You have to customize Perl::Critic to your own requirements. For example, i have upped the "maximum complexity score" and "maximum length of functions" of some parts of my code quite a bit. When you write complex state machines that (for example) handle HTTP connections. the main state machine winds up to be quite long. Yes, i could split that up into more functions, but in my case it would hinder readability and up the mental complexity while debugging.

Perl::Critic is certainly a helpful tool. But only after adapting it to the projects requirements and coding style. Plus, P::C regularly behaves stupid when new Perl features come out.

It's also important to remember that P::C only does static analysis. But only you can prevent forest fires the perl interpreter can properly parse Perl. And some P::C recommendations might even go against project/company policies.