Four tools with complete schemas and basic descriptions, but significant gaps in parameter documentation and error guidance. Tool names follow verb_noun convention (anki_add_note, anki_create_deck, anki_get_decks). Descriptions are present but minimal (10-40 chars), below the 50-200 char LLM-optimized baseline. Parameters lack descriptions in anki_add_notes (cards array items have no descriptions). No output schema documentation. Error handling returns text responses but lacks recovery guidance or categorization. No tool annotations (readOnlyHint/destructiveHint). Composition is reasonable: separate tools for single/batch operations, though batch variant (anki_add_notes) could be better integrated.

• Expand tool descriptions to 50-200 chars. Example: 'anki_add_note' → 'Add a single flashcard to an Anki deck. Use this for one-off cards; use anki_add_notes for bulk imports. Requires AnkiConnect running on localhost:8765.'
• Add descriptions to all parameters. For anki_add_notes.cards, document: 'Array of flashcard objects. Each object must have front (string) and back (string) fields.'
• Document output schemas in tool descriptions. For anki_get_decks, state: 'Returns a JSON object mapping deck names to deck IDs, e.g. {"Default": 1, "Spanish": 2}.'
• Add tool annotations to Tool definitions. Set destructiveHint=true for add/create tools, readOnlyHint=true for get_decks. Update tool-definitions.ts to include these fields.
• Enhance error responses with recovery guidance. Example: 'Failed to create deck: deck already exists. Call anki_get_decks() to list existing decks.' Categorize errors as retryable (connection timeout) vs user-fixable (deck name invalid).