The NotesManager server provides three basic tools with minimal documentation. All three tools have schemas with proper JSON types and descriptions, which is the baseline. However, descriptions are extremely brief (8-34 characters), parameter descriptions are generic, and there is no output schema documentation. Error handling is absent, tools return plain strings with no guidance for recovery or retry logic. The tool names follow verb_noun convention (add_note, list_notes, search_notes) but lack depth in their descriptions. Missing: pagination controls, output schema documentation, error classification, recovery guidance, idempotent operation hints, and composition guidance. The server implements basic CRUD without acknowledging the 54 agentic patterns or the needs of LLM-based agents.

• Expand tool descriptions to 100-200 characters. Include WHAT the tool does, WHEN to use it, and what it returns. Example: 'add_note: Add a note to the database with a title and content. Useful for capturing ideas, todos, or reminders. Returns a confirmation message with the note ID. Duplicate titles are allowed; each note gets a unique ID.'
• Document output schemas. Instead of returning plain strings, return JSON objects: add_note → {success: bool, note_id: int, message: string}; list_notes → {notes: [{id, title, created_at}], total: int, limit: int}; search_notes → {results: [{id, title, content}], query: string, count: int}.
• Add pagination to list_notes: accept limit (default 20, max 100) and offset (default 0) parameters. Return total_count and has_more for agents to iterate through large note sets without loading entire database.
• Add input validation and error guidance. If title is empty, return {error: 'Title required and must be 1-500 characters'}. If search_notes finds nothing, return {results: [], count: 0, suggestion: 'Try a shorter query or different keywords'}. Categorize errors as retryable (timeout, rate limit) vs user-fixable (invalid input).
• Add tool annotations: mark list_notes and search_notes with readOnlyHint=true; mark add_note with destructiveHint=true to signal agents this creates permanent records. Add idempotentHint=true to search/list tools (safe to retry); omit from add_note to signal non-idempotency.
• Add parameter constraints and defaults. Example: 'title: string, 1-500 chars, required'; 'content: string, 1-10000 chars, required'; 'query: string, 1-100 chars, required, case-insensitive'. Defaults: limit=20, offset=0.