With these parameters you can limit the scope, to which filtering by annotations applies. (That is the classes that may be excluded from the documentation according to any filtering by annotation criteria -- both explicit and implicitly ones).

The limitation is needed because since filtering by annotations potentially extends to all classes involved (including those contained in pre-compiled Java libraries), it may have unwanted side effects.

For instance, when you include only classes marked with the specified annotations (using "Filter Classes & Members | By Annotations | Include | Classes" parameter), without any limitation to what this applies, all standard Java SDK classes (e.g. even `java.lang.Object`) will get excluded from being mentioned as ancestors of your classes. That will be wrong, of course! But even more surprising would be to see all public fields and methods of those standard Java classes to show up in your documentation as if they are defined in your own classes you document.