Four tools with explicit schema registration visible in src/index.ts. All tools have descriptions (10-60 chars), but most are concise to the point of being terse. Input schemas are properly JSON Schema with type definitions. However, many parameters lack descriptions: load_snapshot has no parameter descriptions for 'id' and 'name'; list_snapshots has no description for 'limit'; delete_snapshot has no description for 'id'. The save_snapshot tool has the most complete schema with nested properties and descriptions, but even it lacks guidance on the oneOf branching logic (when to use string vs object context). Error handling is generic ('Error: {message}') with no recovery guidance. No output schemas documented. No idempotence or side-effect semantics declared. Tool composition is reasonable (separate save/load/list/delete), but no chaining context IDs are returned from load_snapshot, it returns a prompt string but not snapshot metadata needed for subsequent operations.

• Add descriptions to all parameters: for load_snapshot, explain that 'id' is an integer snapshot ID, 'name' is an optional snapshot name (string), and at least one should be provided; omitting both loads the latest snapshot. For list_snapshots, explain that 'limit' is optional (default 100, max 1000) and controls how many snapshots to return. For delete_snapshot, explain that 'id' is required and must be an integer matching an existing snapshot.
• Document output schemas for all tools. For save_snapshot, return an object with {id: number, name?: string, created_at: string}. For load_snapshot, return {id: number, name?: string, summary: string, context: string, next_steps?: string, created_at: string} so agents can chain operations. For list_snapshots, return {snapshots: [{id, name, summary, created_at}], total: number}. For delete_snapshot, return {id: number, deleted: true}.
• Enhance error messages with recovery guidance. When snapshot not found, suggest: 'Snapshot with ID {id} not found. Call list_snapshots() to see available snapshots.' When no snapshots exist, offer: 'No snapshots found. Create one with save_snapshot().'
• Clarify save_snapshot semantics: state explicitly that it creates a new snapshot and is not idempotent (repeated calls create duplicates). Consider adding an optional 'replace_if_named' parameter to support overwriting a named snapshot instead of creating a new one.
• Add a confirmation pattern to delete_snapshot. Include a 'confirm' parameter (default false) and document: 'If confirm=false (default), return a confirmation prompt asking the user to confirm. If confirm=true, delete immediately.' This prevents accidental deletion.