Notion MCP server has significant definition quality gaps. Tool descriptions are present but minimal (10-50 chars, well below the 50-200 char LLM-optimized baseline). Input schemas are visible in code but lack formal JSON Schema structure with explicit type declarations and constraints. Parameters have descriptions but many are generic ('선택사항' = optional, no guidance on format/range). No output schemas documented. Error handling is absent, no recovery guidance, no categorization of retryable vs fatal errors. YouTube script tools are domain-misaligned (not Notion-related). Composition issues: create_page and update_page both modify content but lack idempotency guarantees or confirmation patterns for destructive operations.

• Expand all tool descriptions to 50-200 chars. Include WHAT (action), WHEN (use case), and state-modification warnings. E.g., 'Search Notion pages and databases by title or content. Returns up to 20 results with IDs for chaining. Use before get_page to find a page by name.'
• Document output schemas for all tools. Specify returned fields, types, and which IDs/references are safe to pass to other tools. E.g., search_notion should return [{id, title, type, url}] so LLM knows to use 'id' for get_page.
• Convert free-form parameters to enums where applicable. Change filter_type to enum ['page', 'database']. Add JSON Schema constraints to properties dict in create_database_entry.
• Add error handling guidance. Document what errors each tool can return (e.g., 'Invalid page_id: not found'), whether they are retryable, and what the LLM should do next (e.g., 'Try search_notion to find the correct page ID').
• Separate YouTube script tools into a distinct server or remove them. If retained, document their relationship to Notion and add file path validation to prevent directory traversal in delete_youtube_script.

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

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