Server has 21 tools with explicit schemas and descriptions visible in src/index.ts. However, quality is inconsistent. Naming follows verb_noun convention (good), but many descriptions are generic or lack actionable context. Parameter descriptions are present but often minimal (10-30 chars). No output schemas documented. Error handling is basic, no recovery guidance or error classification. Destructive tools (clear_nexus, manage_packages, create_nextjs_app) lack confirmation patterns. Many tools expose implementation details (e.g., packageManager enum) rather than abstracting complexity. Composition issues: create_entities + create_relations could be unified; multiple Notion tools (search, get_database_content, get_page_content) lack clear differentiation.

• Document output schemas for all 21 tools. Example: 'Returns {success: boolean, entities: [{id: string, name: string, nodeType: string}], errors?: string[]}'. This enables LLMs to chain tools and extract required fields.
• Add error handling with recovery guidance. Example for scrape_page: 'If URL is invalid, return {error: "Invalid URL format. Expected https://...", retryable: false}. If timeout, return {error: "Page took >30s to load", retryable: true, suggestion: "Try a simpler URL or check network"}.'
• Expand parameter descriptions to 50-200 chars with format constraints. Example: 'baseUrl (string, required): Base URL of documentation site (must start with https://, e.g., https://docs.example.com). Crawler will follow links within this domain.'
• Implement confirmation pattern for destructive tools. clear_nexus should return {status: 'pending_confirmation', message: 'This will delete all Nexus data. Call confirm_clear_nexus(confirmation_id) to proceed.'} before executing.
• Consolidate overlapping Notion tools. Merge search_notion, get_database_content, and get_notion_page_content into a single search_notion(query, type: 'page'|'database'|'all') tool with clear type-based behavior.