Debugging a Deceptive API Error: When 'Empty Content' Means 'Ran Out of Tokens'

A developer debugging a multi-agent pipeline found that a model returned empty content with finish_reason "length". The real issue was that the reasoning model's chain-of-thought consumed the entire token budget, leaving nothing for visible output. The fix involved raising maxTokens and improving error messages to distinguish transport failures from budget exhaustion.