Server has 20 tools with consistent naming (verb_noun pattern) and complete input schemas. Descriptions are present but generic (avg ~60 chars, below 194-char baseline). Parameters have types and descriptions, but lack enums for constrained values (priority, view_mode). Output schemas are not documented. Error handling exists but is generic. No tool annotations (readOnlyHint, destructiveHint). Missing pagination for list operations returning potentially large result sets.

• Add JSON Schema enums for priority (0, 1, 3, 5) and view_mode ('list', 'kanban', 'timeline') to prevent LLM hallucination of invalid values.
• Document output schemas for all tools. Example: list_tasks should return {tasks: [{id, title, content, due_date, priority, status, tags}], total_count: number}.
• Add pagination parameters (limit: 1-100, offset: 0+) to list_tasks, list_projects, get_all_tasks, get_completed_tasks, search_tasks. Cap default limit at 20-50 and document in descriptions.
• Add tool annotations: mark delete_task and delete_project with destructiveHint=true; mark read-only tools (get_*, list_*, search_*) with readOnlyHint=true; mark idempotent operations (complete_task, reopen_task) with idempotentHint=true.
• Expand batch_create_tasks input schema to explicitly define the structure of each task object in the array (required: title; optional: content, due_date, start_date, priority, project_id, tags).