LM Arena Proves Claude Opus 5 Writes 3x More but Simpler

Claude's writing has been changing under the hood, and now there's data to prove it. Arena.ai analyzed tens of thousands of real-world, high-reasoning outputs from Claude Opus 4.5 and Opus 5 collected through its Text Arena. Opus 5 writes more, structures sentences more elaborately, and uses simpler vocabulary than its predecessor.

What Arena actually is

Arena (formerly Chatbot Arena) is a public, web-based platform that evaluates large language models. Users enter prompts for two anonymous models to respond to and vote on the better response, after which the models' identities are revealed. As of early 2026, Arena has over 5 million monthly active users across 150 countries and processes more than 60 million conversations per month. That scale means the writing data being pulled from is genuinely representative of how these models behave in the wild, not in a lab.

Longer, more elaborate, but simpler words

The headline stat is hard to ignore. Opus 5 averages 510 words per response, compared to 158 for Opus 4.5, a 3x increase in output length. The shift goes deeper than word count:

• 58% rise in average sentence length from Opus 4.5 to Opus 5
• 46% rise in clause frequency (how often sentences contain embedded sub-clauses)
• 6.8 percentage point drop in long content words (from 46.9% to 40.1%)
• 53% drop in abstract nouns (from 6.02 to 3.79 per 1,000 words)

That last pair is the surprising twist. Opus 5 builds longer, more structurally complex sentences, then fills them with simpler, more concrete words. The model has become more elaborate in structure while becoming more accessible in vocabulary. Whether that reflects a deliberate design choice or an emergent artifact of training is an open question.

The stylistic fingerprints everyone is noticing

Beyond raw length, Arena's analysis quantified the specific writing habits that have been driving developers up the wall:

• 2.3x as many em dashes compared to Opus 4.5
• ~2x as many phrases like "load-bearing" (a construction that shows up in code comments, architecture docs, and commit messages)
• 50% more honesty wording like "honestly" and "frankly"

Claude Opus 5 says "load-bearing" constantly, along with a stable set of other prose tics. The phrase has become so notorious that it spawned its own Hacker News thread with over 1,700 points. The line that crystallized it was posted to r/ClaudeAI: "That is deliberate and load-bearing rather than tidy." It is a real sentence, written by a real model, about a dotnet publish build step. The metaphor is doing no work. Nothing is bearing any load.

The em dash problem has its own ecosystem of workarounds. Claude learned to write by analyzing high-quality text from books, academic papers, journalism, and professional publications. Those sources use em dashes more frequently than casual human writing. The model learned that em dashes appear in polished prose, so it defaults to them constantly, not understanding that overuse creates a monotonous, recognizable pattern.

Why this is probably happening

Anthropic hasn't published an explanation, but the community has a leading theory: reinforcement learning from human feedback (RLHF) is rewarding prose that reads as confident, dense, and quotable. When human raters consistently prefer the punchier of two drafts, the model gets trained toward a narrow band of high-scoring constructions over many iterations. "Load-bearing" is efficient in exactly that way: one hyphenated adjective that asserts structural importance without having to argue for it.

Claude Opus 5's default user-facing responses run longer than prior Opus models'. The effort parameter controls how much the model thinks, rather than how much it says. That distinction trips up a lot of people: lowering the effort setting will not reliably shorten Opus 5's responses. Anthropic's documentation states this directly. Effort controls thinking volume, not visible response length.

How Fable 5 compares

Arena's analysis also included Fable 5, Anthropic's frontier model, as a comparison point. The contrast is striking. Fable 5 runs 38% more concise than Opus 5, averaging 316 words per response versus 510. It compensates in a different direction: nearly 2x as likely to include praise or validation, and more likely to open with phrases like "yes, exactly." Different stylistic fingerprint, same underlying tendency toward performative language.

What developers are doing about it

Developers have slammed Opus 5's default verbose and backhanded responses, over-engineered solutions, and need for major prompting changes, with some switching to older versions or rivals. The community has converged on a practical fix: generic instructions fail. "Write better" and "be concise" do essentially nothing. What works is naming the specific tics.

A CLAUDE.md block that actually works looks like this:

## Writing style
- No em dashes. Use commas, parentheses, or a new sentence.
- Banned phrases: "load-bearing", "worth stating plainly", "full stop",
  "carry the argument", "isn't just X , it's Y".
- No punchy fragments for drama. Write complete sentences.
- Do not build to a turn of phrase. State the claim directly.
- Technical documentation, not marketing copy.

The key insight from the community is that Claude caught the gist without needing every tic enumerated. "Punchy" seemed to be the operative word. That is the single most useful finding in the whole discussion. You're naming the optimization target and telling the model to stop pursuing it, rather than blacklisting strings. A short, direct instruction works: tell it to keep responses focused, keep caveats brief, spend most of the response on the main answer, and give a high-level summary unless you ask for depth.

What this tells us about model evolution

The Arena data offers a rare look at how a model's writing personality shifts between versions, measured at scale across real tasks rather than synthetic benchmarks. The pattern that emerges is consistent with a model being optimized for perceived quality over actual quality: longer, more elaborate, more confident-sounding, without necessarily being more precise or informative.

Claude Opus 5 is built for complex agentic coding and enterprise work, with particular strengths in long-horizon agentic tasks. For those use cases, the verbosity might be a reasonable tradeoff. For documentation, code comments, or any context where brevity signals understanding, the default behavior works against you. The fix is explicit prompting, and now you have the data to know exactly what to target.