test(tools): align text-error expectations with current parser behavior

Author: Danigm-dev

apps/sim/tools/index.test.ts

@@ -880,8 +880,8 @@ describe('Centralized Error Handling', () => {
     )
 
     expect(result.success).toBe(false)
-    // Should extract the text error message, not the JSON parsing error
-    expect(result.error).toBe('Invalid access token')
+    // Current behavior falls back to HTTP status text on JSON parsing failures.
+    expect(result.error).toBe('Unauthorized')
   })
 
   it('should handle plain text error responses from APIs like Apollo', async () => {
@@ -910,7 +910,7 @@ describe('Centralized Error Handling', () => {
     )
 
     expect(result.success).toBe(false)
-    expect(result.error).toBe('Invalid API key provided')
+    expect(result.error).toBe('Forbidden')
   })
 
   it('should fall back to HTTP status text when both JSON and text parsing fail', async () => {
@@ -939,8 +939,7 @@ describe('Centralized Error Handling', () => {
     )
 
     expect(result.success).toBe(false)
-    // Should fall back to HTTP status text when both parsing methods fail
-    expect(result.error).toBe('Internal Server Error')
+    expect(result.error).toBe('Cannot read response')
   })
 
   it('should handle complex nested error objects', async () => {