Yeah, that's a tricky one. Ideally there would be an sbt doc generator that builds a web page or markdown file for you.

And for a key you often need multiple pieces of information: the key name for calling/inspecting in the sbt shell, `lessSilent`, and possibly its normal scope, `web-assets:lessSilent`; the full path to the key for using in code, `com.typesafe.sbt.less.SbtLessPlugin.LessKeys.silent`; and then the auto-imported version for using in build.sbt or with the set command, `LessKeys.silent in WebKeys.Assets`.