What reasons make the use of the 'throws' keyword undesirable in method declarations?

Using the throws keyword in a method declaration can be undesirable for several reasons:

• API complexity: A method declaring throws forces the calling code to handle or propagate the exception, increasing complexity.
• Reduced readability: A large number of declared exceptions makes it harder to understand which errors can actually occur.
• Tight coupling: If a method declares checked exceptions, changes in exceptions require changes in the calling code.

Therefore, it is often preferred to use unchecked exceptions (subclasses of RuntimeException), which do not require declaration in throws, simplifying error handling and making the code more flexible.