Two tools with minimal but present schemas and descriptions. Both tools have clear verb-noun naming (add_task, list_tasks) and basic parameter documentation. However, descriptions are extremely brief (10-20 chars), falling below the 34-char p10 baseline for production tools. No output schema documentation. No error handling guidance. Parameter descriptions lack format/constraint details. Missing idempotency guidance for add_task (write operation). No pagination metadata in list_tasks despite accepting a limit parameter.

• Expand add_task description to 50-150 chars: 'Add a new task to the todo list. Returns the created task with id, title, and created_at timestamp. Each call creates a unique task; retrying with the same title will create duplicates.'
• Expand list_tasks description to 50-150 chars: 'Retrieve tasks from the todo list, sorted by creation date (newest first). Returns an array of task objects. Use limit to cap results (1-500, default 100). Returns total_count for pagination awareness.'
• Document output schemas in tool docstrings or via a schema registry. Example: add_task returns {id: int, title: string, created_at: ISO8601}; list_tasks returns {tasks: [{id, title, created_at}], total_count: int}.
• Add try-catch blocks with actionable error messages. E.g., 'Failed to load tasks: file not found at {TASKS_PATH}. Ensure TASKS_PATH environment variable is set and the file exists.' instead of raw exceptions.
• For list_tasks, return {tasks: [...], total_count: N, has_more: bool} instead of bare array. This enables pagination awareness and prevents context window exhaustion.