Critical deficiencies across all dimensions. 18 of 37 tools (49%) lack descriptions entirely (get-project, get-projects, get-section, get-sections, get-shared-labels, get-task-comments, get-task, get-tasks-by-filter, get-tasks, move-task-to-parent, move-task-to-project, move-task-to-section, remove-shared-label, rename-shared-label, reopen-task, update-comment, update-label, update-project, update-section, update-task). All 37 tools have parameter descriptions set to null, violating the requirement that every parameter must have a description. Input schemas are present but parameter documentation is completely absent. No output schemas are documented. Error handling is generic (PostHog exception capture with JSON stringification). Tool names follow verb_noun convention (positive), but lack of parameter guidance and missing descriptions severely limit LLM usability.

• Add non-empty descriptions to all 18 tools currently lacking them (get-project, get-projects, get-section, get-sections, get-shared-labels, get-task-comments, get-task, get-tasks-by-filter, get-tasks, move-task-to-parent, move-task-to-project, move-task-to-section, remove-shared-label, rename-shared-label, reopen-task, update-comment, update-label, update-project, update-section, update-task). Each description should be 50-200 characters and explain WHAT the tool does, WHEN to use it, and any prerequisites.
• Replace all null parameter descriptions with actionable text. For example, 'projectId' should be 'The unique identifier of the Todoist project (string, required)'. For enums like 'color', list valid options: 'Color theme for the label: berry_red, light_blue, red, blue, orange, grape, yellow, violet, olive_green, lavender, lime_green, magenta, green, salmon, mint_green, charcoal, teal, grey, sky_blue'.
• Document output schemas for all tools. For example, add-task should document: 'Returns {id: string, content: string, projectId: string, completed: boolean, createdAt: string}'. This enables LLMs to chain tool calls and extract required data.
• Implement structured error handling with recovery guidance. Replace generic JSON.stringify(error) with categorized errors: 'User not found. Try get-project-collaborators() first to find valid assignee IDs.' or 'Invalid priority: must be 1-4. Got: 5'.
• Add tool annotations (readOnlyHint, destructiveHint, idempotentHint) to all tools. Mark get-* tools with readOnlyHint: true. Mark delete-* tools with destructiveHint: true. This helps LLMs reason about safety and retry logic.