## Why is this an issue?

Nullability annotations in Java are used to indicate whether a variable or parameter can be assigned a null value or not. These annotations help to prevent Null Pointer Exceptions and improve the reliability of code.

Redundant nullability annotations can clutter the code and make it harder to read and understand. When a nullability annotation is already implied by the context or by other annotations, explicitly adding it again only adds noise and makes the code less clear.

Removing them improves code readability, maintainability, reduces the risk of inconsistencies, and ensures that the remaining annotations carry meaningful information.

### Noncompliant code example

JSpecify code example:

    @NullMarked
    class MyClass {
      public void method(@NonNull Object o) { // Noncompliant: @NonNull is redundant here
        // ...
      }
    }

### Compliant solution

    @NullMarked
    class MyClass {
      public void method(Object o) {
        // ...
      }
    }