These tools could be used to turn code smells, duplication, and poorly written tests into a total "score" for well-written code. Although this should hardly be the way code is evaluated.
Also, complex code that isn't written "the best way" isn't so bad. It incurs technical debts. Like financial debt, technical debt can be very good if used properly--or end with disastrous results if used irresponsibly. So let some component of a code base bloat if you need to hit a deadline so long as you're going to refactor later.