Problem\n\nThe current fetch tool implementation doesn't properly handle HTTP 4xx errors, particularly:\n\n1. 400 Bad Request errors: These should be retried with potential fixes to the request.\n2. 429 Rate Limit Exceeded errors: These should implement exponential backoff and potentially switch to a "slow mode" to avoid hitting rate limits.\n\n## Proposed Solution\n\n1. Implement retry mechanism for 400 errors with potential request fixes\n2. Implement exponential backoff for 429 errors\n3. Add a "slow mode" option that can be enabled when rate limits are encountered\n4. Improve error logging to provide more context about failed requests\n\n## Technical Details\n\nThe implementation will be in the fetch tool located at:\n\n\nThis will help make the API interactions more robust and prevent failures due to rate limiting or temporary issues.