It's a pain because it forces users to consider and code against error paths.
Just like putting on a seat belt is a pain.
Both are pains that are worth having because they help you create robust software.
The ways in which a function can fail should absolutely be part of its signature, and if these are recoverable, the compiler should refuse to build until you either handle these errors or pass them on to the caller.