There should be human-written, descriptive words written for every item in the API docs (or at least all the important items...which is probably all of them). For example, on the base page I linked to before, in the Description column there should be a...umm, what's it called. Oh yes, a description. For every package listed. And when you navigate to a particular class or package, there should be words there, too. Words that help the user understand what all the objects, classes, and methods are for and what they do. Important classes should be well-documented, in particular. For example, https://www.soapui.org/apidocs/com/eviware/soapui/impl/wsdl/testcase/WsdlTestCase.html has only "TestCase implementation for WSDL projects" for documentation. Which I think is no longer even true (I think it's also used for WADL projects, yes?). And the only method that is documented is the moveTestStep method (and even that documentation could be better; what does a positive offset mean? what does a negative offset mean? what happens if you try moving a TestStep by an invalid offset (too large or too small)?).
Basically I just think that it would be nice if the API documentation consistently had content beyond the nearly useless Javadoc auto-generated content.