NeuroVault defines 19 tools with basic schemas and descriptions, but exhibits significant gaps in parameter documentation, output schema clarity, and error handling guidance. Tool names are action-oriented (recall, remember, reset) and descriptions exist for all tools (ranging 50 - 150 chars), meeting baseline presence requirements. However, most parameter descriptions are minimal (10 - 30 chars), and output schemas are not documented in the visible code. The 'reset' tool with destructive capability lacks confirmation/dry-run patterns. No tool annotations (readOnlyHint, destructiveHint) are visible. Error handling is absent, no recovery guidance, retryability classification, or actionable error messages. Composition is reasonable (tools are single-purpose), but chaining support is unclear due to missing output documentation.

• Document output schemas for all tools. For 'recall', specify: {engrams: [{id, title, content, relevance_score}], total_count, next_cursor}. For 'graph', specify: {nodes: [{id, label, type}], edges: [{source, target, weight}]}. This enables LLMs to chain tools and extract required fields.
• Add confirmation/dry-run pattern to 'reset'. Introduce a 'dry_run' boolean parameter (default false) that returns what would be deleted without executing. Require explicit confirmation for vault=true deletions.
• Expand parameter descriptions with constraints and discovery hints. E.g., 'limit: Maximum number of results (1 - 100, default 20)' and 'brain_id: UUID of the brain to scope. Call brains_list() to discover available brains.' This reduces LLM guessing and failed calls.
• Add error handling guidance to tool descriptions. E.g., 'recall: Returns empty results if no engrams match the query. If unexpected, try a broader query or call notes_list() to verify vault is populated. Retryable on timeout.'
• Implement tool annotations in schema. Add readOnlyHint: true to recall, notes_list, graph, audit_recent, brains_list, brains_active, brains_stats, health, version, status. Add destructiveHint: true to reset. Add idempotentHint: true to remember, observations, journal_event (if they upsert by title/timestamp).