> What are API specification supposed to do if not specify the behavior of
the API?

Well, there are two parts of every specification: what's in scope and
what's out of scope. If we want to provide our users with a guarantee about
limits, then those limits should be specified, and we should make some
specs. Currently, that behavior is out of the scope of the spec.

> No network supports transactions of that size.

TIL. Cool.

> To clarify, what happens when a Balanced engineer returns a message in an
error that doesn't make sense but is in the schema?

Ahhhhhhhhhh! Light bulb. I didn't realize you were speaking about one of
ours, sure.

Yes, it is true that someone could return something that's part of this
array, but the wrong one. However, given how brittle those kinds of specs
are, and the fact that this text is purely informative, I don't believe
that including it inline for that purpose has positive gain. There's a lot
to lose and little to gain.