TaskTracker has clear tool names following verb_noun conventions (add_task, complete_task, delete_task) and provides descriptions for each tool. However, there are significant gaps in parameter-level documentation, error handling guidance, and output schema documentation. The server implements 3 tools with basic functionality but lacks the rigor expected for production use. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are present despite delete_task being a DESTRUCTIVE operation. Parameter descriptions exist but are minimal (under 30 chars). Output schemas are not documented, LLMs cannot predict the response structure. Error handling returns unstructured responses with no recovery guidance.

• Add explicit output schema documentation for each tool. For add_task, document: {id: integer, title: string, description: string, status: 'pending'|'completed', created_at: ISO8601 string}. For complete_task: {id: integer, status: 'completed', completed_at: ISO8601 string} or {error: string}. For delete_task: {success: boolean, deleted?: {...}} or {success: false, error: string}.
• Enhance error responses with recovery guidance. Instead of {'error': 'Task 5 not found'}, return {'error': 'Task 5 not found. Call list_tasks() or get_all_tasks resource to see available task IDs.'}
• Add destructiveHint annotation to delete_task schema. Update the tool definition to include 'destructiveHint': true in the FastMCP decorator or schema, signaling to agents that this call is irreversible.
• Implement a confirm_delete_task tool or add a 'confirm' parameter to delete_task. Require agents to call confirm_delete_task(task_id, confirmation_token) after a delete request returns a one-time token, preventing accidental deletion.
• Expand parameter descriptions to 40-80 chars each. For task_id parameters, add: 'The ID of the task (a positive integer; available IDs are returned by add_task or visible in get_all_tasks resource).'
• Document parameter constraints in descriptions. For title in add_task, add: 'A non-empty string (1-200 characters) describing the task title.'
• Switch to persistent storage (e.g. SQLite, PostgreSQL) instead of in-memory list. This enables tasks to survive server restarts and serves multi-session workflows.