Four tools with clear verb-noun naming (add-todo, list-todos, toggle-todo, delete-todo) and basic descriptions. All tools have input schemas with type definitions and required fields. However, descriptions are minimal (10-60 chars, below the 50-200 char LLM-optimized baseline), parameter descriptions lack depth, output schemas are undocumented, and error handling is absent. No recovery guidance, no actionable error messages, and no confirmation pattern for destructive operations. Schemas are present but sparse, missing details on output structure, pagination, and field semantics.

• Expand tool descriptions to 50-200 chars. Example: 'add-todo: Create a new todo item. Returns the created todo with id, description, and done status. Use this when the user wants to add a task to their list.'
• Document output schemas for all tools. Specify that add-todo returns {id: number, description: string, done: boolean}, list-todos returns {todos: [...], count: number}, etc.
• Add error handling with recovery guidance. E.g., 'If id not found, return {success: false, error: "Todo #X not found. Call list-todos to see available IDs."}'
• Implement a confirmation pattern for delete-todo: add a 'confirm' boolean parameter or return {success: false, requiresConfirmation: true, message: "Delete todo #X? Call delete-todo again with confirm=true."}'
• Enhance parameter descriptions with constraints. E.g., 'id: The numeric todo ID (1, 2, 3, ...). Must exist or the operation will fail.'