Address code review feedback - Improve test quality and add TODO comments

- Replace assert.AnError with realistic fmt.Errorf() in tests
- Add TODO comment acknowledging string-based error matching limitations
- Suggest future improvement to use type assertions for error classification

Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>

Author: Copilot

internal/mcp/connection.go

@@ -24,7 +24,9 @@ import (
 var logConn = logger.New("mcp:connection")
 
 // isHTTPConnectionError checks if an error is a network connection error
-// This helper reduces code duplication for checking common connection error patterns
+// This helper reduces code duplication for checking common connection error patterns.
+// Note: Uses string matching which is fragile but consistent with existing patterns in the codebase.
+// TODO: Consider using errors.Is() or type assertions (*net.OpError) for more robust error classification.
 func isHTTPConnectionError(err error) bool {
 	if err == nil {
 		return false

internal/server/call_tool_result_test.go

@@ -162,7 +162,7 @@ func TestNewErrorCallToolResult(t *testing.T) {
 	}{
 		{
 			name:        "simple error",
-			err:         assert.AnError,
+			err:         fmt.Errorf("test error"),
 			expectError: true,
 		},
 		{