Audit usage of @inheritDoc

We're using `@inheritDoc` to avoid writing javadoc, but that's not well founded in some cases. Audit the usage of it and ensure our docs are reasonable.

Start by searching the repository for every use of @inheritDoc and review the surrounding Javadoc for whether inherited documentation is appropriate. The work is done when each use has reasonable, intentional documentation, but the issue does not name specific files or tests.

Written by the indexing model from the issue text.