Server has 11 tools with complete input schemas and descriptions in Chinese. Naming follows verb_noun pattern (get_, create_, update_, delete_) consistently. However, descriptions lack depth, most are 1-2 sentences without guidance on when to use each tool, prerequisites, or return value structure. Parameter descriptions are present but minimal. Output schemas are not documented. Error handling is absent from tool definitions. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (READ_ONLY, WRITE, DESTRUCTIVE). Schemas are well-formed JSON Schema with proper types and enums, but lack examples of return structures.

• Add tool annotations to all tools: readOnlyHint=true for get_* tools, destructiveHint=true for delete_* tools, idempotentHint=true for get_* and complete_task. This enables agents to reason about side effects.
• Document output schemas for each tool. E.g., 'Returns: {project_id: string, name: string, color: string, view_mode: string, kind: string, created_at: ISO8601, updated_at: ISO8601}'. Include chaining IDs (project_id in create_project response so agents can immediately call get_tasks).
• Expand descriptions to 80-150 chars with WHAT/WHEN/RETURN structure. E.g., 'Create a new task in a project. Use when user says "add task". Returns task_id, title, due_date, priority, status. Supports subtasks, reminders, and recurrence rules.'
• Add parameter-level guidance for complex fields. For create_task.items (subtasks), document the expected structure: 'Array of subtask objects. Each must have title (string), optional status (0=incomplete, 2=complete), optional start_date (YYYY-MM-DD).'
• Implement error handling in tool implementations (not visible in schema but critical): validate date formats (YYYY-MM-DD), validate color hex patterns, validate priority enums, return actionable errors like 'Invalid due_date: expected YYYY-MM-DD, got "2024-13-45". Please use a valid date.'.