One person’s helpful metadata is another person’s noise. It’s much better for a door to visually indicate that it should be pushed open than to put up a sign there.

However, doing the former requires a level of empathy with humans that LLMs rarely have.

Human brains have caloric demands. It is possible for humans to process enormous amounts of unrelated facts to make a decision, but it’s tiring. It’s much better to not do that, especially just to get some basic information.

To anthropomorphize a bit, an LLM might find it charming and interesting to read someone’s life story as a preamble before their taco recipe. Humans by and large find that annoying, not because we can’t understand the biography but because processing that information is not free.

So it’s probably possible to design using an LLM. You would probably have to be intentional about it.

If you don't have any kind of agent instructions saying "don't copy code into prose", you'll inevitably get text that reflects some previous state of the system instead of its current state.

It's fine in isolation to have help text for complex interfaces needing explanation. Better yet contextual hints.

But there's about 10 other examples explaining intention of the coding rather than immediately useful information to the user, it's all over this one site in small grey text. And I guarantee you nobody is reading them carefully. Just like how nobody likes reading a 15 line LLM code comment over a simple function.

Most of it could be better solved with more thoughtful design or deleted. The link explanation is particularly egregious.