Two read-only tools with basic schemas and minimal descriptions. Tool names follow verb_noun pattern (list_tasks, get_task) but descriptions are terse (under 100 chars) and lack actionable context. No output schema documented. Error handling minimal (only get_task validates taskId). No parameter constraints (enums, ranges). Descriptions do not explain WHEN to use each tool or what fields are returned.

• Add parameter descriptions to all inputs. For list_tasks: 'status: Filter by task status (e.g., pending, completed). keyword: Search task names/descriptions. limit: Max results to return (1-100, default 20).'
• Document output schema. Specify what fields list_tasks returns (e.g., tasks: [{id, name, status, created_at}], total_count) and what get_task returns (id, name, status, details, created_at, updated_at).
• Expand tool descriptions to 100-200 chars. Example: 'List all tasks with optional filtering by status or keyword. Returns paginated results. Call this first to discover available tasks before fetching details with get_task.'
• Add constraints to parameters. Declare status as enum (pending|completed|failed), limit as integer with min=1, max=100, default=20.
• Enhance error messages with recovery guidance. E.g., 'Task not found. Call list_tasks() to see available task IDs.' Return structured error: {ok: false, error: 'TASK_NOT_FOUND', suggestion: 'Call list_tasks()'}.