Four tools with complete schemas and descriptions. Naming follows verb_noun convention (create, update, delete, search). Descriptions are concise (20-80 chars) but lack actionable context for LLM selection. Parameter descriptions present but minimal. No output schema documentation. Error handling absent, tools return success text only, no guidance for failure cases. Missing idempotency hints for write operations. No pagination for search results despite accepting a limit parameter.

• Document output schema for each tool. Example: 'Returns {id: string, title: string, body: string, tags: string[], createdAt: ISO8601, updatedAt: ISO8601}'. This enables LLMs to chain tools and extract required fields.
• Add error recovery guidance. Example for notes.update: 'If note not found, call notes.search() to locate the correct ID.' For notes.delete: 'Deletion is permanent. Confirm the note ID before calling.'
• Expand parameter descriptions to 50-100 chars with constraints. Example: 'tags: Array of lowercase alphanumeric tags (max 5 per note, 20 chars each). Used for filtering and organization.'
• Add dry-run or confirmation step to notes.delete. Return {id, title, preview} and require explicit confirmation before permanent deletion.
• Enhance notes.search to return pagination metadata: {results: [...], total: number, limit: number, offset: number}. This prevents context window exhaustion on large note collections.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry