1) The appropriate metric for 'well written' is that you can read the whole thing aloud and understand the findings in the time it takes a person to eat a sandwich, a bag of chips, and drink a medium coffee. About 75 minutes. Anything more may be 'read' but not understood and anything less means you should have done more work.
2) Everyone loves jargon. The more obscure words the better. The more complicated and obfuscated, the better. I find that I want to grok the research. Most of my compatriots do not want to do that. However, we all think the same thing about everyone else. More complicated papers result in a 'treasure hunt' mentality that many researchers actually enjoy, it seems. The journal club evolved into a 'tennis game' of sorts where the submitter would lord over the others about their knowledge of the paper. i don't want to generalize too much, but I think this behavior of 'one-up-man-ship' and 'I-know-more-than-yoooou-dooo' is core to academia.
Some personalities like long explanations, some do not.
Beware that your personality will often miss important details that would be in the verbiage.
Those or like reading often waste too much time reading unnecessary details.
There are pros and cons of both.
(I hope I wrote that in the style you would like to read)
But when you are communicating, it is common sense to make sure the important points come across, then only dive into the details. Unfortunately that is not always something you are incentivized to do in academic research, where fumigation is the norm.
I'd also point out that one can be terse and uninformative as well - point in case: most public Git repositories out there.
I enjoy reading, and will often read long pieces -- albeit I would wish they were terser, because often they could be, with no loss of precision.
I have also never met anyone that, even though they like to read like I do, would take pleasure in reading something that drones unnecessarily. When communicating, that is -- plenty of people enjoy the mini-novels put out by Slate, the New Yorker, ... (and me too, sometimes).
I have taken to the habit to summarizing the things I read on my blog. These summaries are of course less informative than the source, but the signal-to-noise ratio is much higher.
When doing a presentation there are other considerations/rules.
Those rules do not apply to the more generic discussion.
Posters are wonderful.
Papers aren't Posters.
> It is an old observation that the best writers sometimes disregard the rules of rhetoric. When they do so, however, the reader will usually find in the sentence some compensating merit, attained at the cost of the violation. Unless he is certain of doing as well, he will probably do best to follow the rules.
Is there any field for which this is not true?
Just ask Louis Slotin. Oh wait. You can't.
As a senior PhD student, the advice I give my younger peers and master students regarding academic posters: you should be able to read it from across the room, or printing in A4 and held at arms' length. Most posters are horribly over-cramed.
I see the same things in academic papers. The length is limited, but many people find a way around by including tons for mathematic, which is much denser. When I take the pain to go through it, I usually find all this math to be unnecessary (but it does give the paper the halo of serious research).