Two tools with minimal documentation. save-todo has a generic description ('Save, create, make, generate, a todo to a file') that conflates multiple intents and lacks clarity on when to use it. get-todo description is missing entirely from visible code. Both tools have basic input schemas with type strings and descriptions, but lack output schema documentation. No error handling guidance, no parameter constraints (enums, ranges), and no indication of idempotency or side effects. Parameter descriptions are minimal (e.g., 'UUID of the todo' does not explain format or constraints). No tool annotations (readOnlyHint, destructiveHint). The schema for save-todo includes three required parameters (todo, time, uuid) but provides no guidance on how to generate or validate UUIDs, or what time format is expected.

• Add a complete description to get-todo: 'Retrieve a single todo item by UUID. Returns the todo object with uuid, time, and todo fields, or null if not found.'
• Rewrite save-todo description to be specific and state side effects: 'Create or update a todo item. Appends a new todo to the todos.json file. Returns success confirmation or error if write fails. Idempotent if uuid is unique.'
• Document output schemas for both tools. E.g., save-todo returns {success: boolean, uuid: string, message: string}; get-todo returns {uuid: string, time: string, todo: string} | null.
• Add format constraints to parameters: time should specify 'ISO 8601 format (YYYY-MM-DDTHH:mm:ssZ)' and uuid should specify 'UUID v4 format (36 characters, lowercase hex with hyphens)'.
• Add tool annotations: mark get-todo with readOnlyHint=true; mark save-todo with destructiveHint=true (modifies file state).