The OAuth2 health-check issue is harder because it requires coordinating token acquisition, MCP health-check execution, authentication edge cases, and regression coverage; the other issue lacks enough detail to indicate comparable implementation scope.

The right issue appears to imply a broader engineering effort with more uncertain scope, while the left appears more likely to be a contained debugging task. The right therefore carries greater implementation risk and investigation overhead.

The right issue has an ambiguous, potentially broad engineering scope, requiring discovery and architectural coordination. The left issue appears comparatively bounded to correcting established cost-processing paths and adding regression coverage.