Standardize error message formatting in update_task and related functions

[chriscarrollsmith]

Standardizing Error Handling in Task Management Functions

Current Issues

• Inconsistent error formatting (JSON-stringified vs direct Error throws)
• Varying levels of detail in error messages
• Lack of structured error information for consumers

Proposed Error Response Format

{
  content: [{
    type: "text",
    text: JSON.stringify({
      status: "error",
      code: "ERROR_CODE", // e.g., TASK_NOT_FOUND, PROJECT_NOT_FOUND, MISSING_DETAILS
      message: "Human-friendly error message",
      details: {
        // Additional context about the error
        entityId: id,
        entityType: "task"|"project",
        fieldName?: string,
        currentValue?: string,
        expectedValue?: string,
        // etc.
      }
    })
  }]
}

Implementation Plan

1. Define Standard Error Interface

   • Create TypeScript interfaces for error responses
   • Ensure consistent structure across all functions

2. Error Code Standardization

   • Define enum/constants for error codes
   • Group by domain (task errors, project errors, validation errors)

3. Update Functions

   • Modify update_task to use the new format
   • Refactor related functions for consistency
   • Add contextual details to all error messages

4. Testing & Documentation

   • Add comprehensive test cases for each error scenario
   • Create documentation with error handling examples
   • Build reference guide for all possible error codes

Benefits

• Consistency: Uniform error format across all task functions
• Clarity: Detailed error information for faster debugging
• Context: Additional information about error circumstances
• Resolution: Guidance on how to resolve common errors
• Documentation: Clear reference for all possible error scenarios

This standardization will improve both developer experience and system robustness by making errors more predictable and informative.