Ask HN: What Makes a Good Datasheet?

I've been browsing a few (RISC-V related) System-on-Chip datasheets. Have seen 1000s of datasheets (ROM/RAM/discrete logic/peripherals, opamps, voltage regulators, etc etc) in my life. Some lacking essential info like Thermal Design Power (TDP), # of balls on the BGA package, etc. One (JH7100) including mention of the standards that were referenced. Nice! Another: lots of spelling errors (Chinese pulled through Google Translate?). Yet another: some value declared, but missing the unit. Yet another: upper/lower case all over the place, CamelCase looking tame in comparison (this seems commonplace though). Also: a simple dictionary of abreviations used. Not all readers are experts!

To be honest: nice looking tables, block diagrams etc do matter. They make a datasheet more readable, and yes "1 picture says more than 1000 words" is true to some degree.

In short: in your opinion, what makes a good datasheet? What should (or should not) be included? What are do's & don'ts when writing one? What's 'added value' in this context?