I'm very thankful that not all developers work in a code factory where explicit requirements get spit out on their desk at the end of the process. If you're involved in the definition you get to prevent the "team <upstream> is so clueless" issues, and actually learn about what you're building beyond code implementation.
I don't think that's what's going on here, though. Developers often don't design UI, anyway. They're given a UI spec or mock-up from a UI/UX designer, and build it to spec. That's not a "code factory", that's just being a professional about it (and many software developers are terrible at UI design and should grow some humility and accept that).
Regardless, a quick "we need this score box to be laid out exactly this way, because this is the standard in this particular fandom, and our fans will expect to read it this way" should be sufficient. A developer who doesn't accept that, and argues, needs to mature and learn some social and professional skills.
Even more desirable is a dev who you can simply ask to make a score box and they deliver some think that meets or exceeds your expectations without further information.
