Both tools have critical definition gaps. markdown_to_epub has a reasonable description (89 chars) and partial schema (4 params with types but missing descriptions for 3 of them). idea_refine has a vague description (67 chars) and minimal schema (1 param, 'action' type string but no enum or valid values documented). Neither tool documents output schemas. No error handling guidance. Tool names lack clear verb-noun structure ('idea_refine' is ambiguous, refine what? how?). Parameters lack actionable constraints and format guidance. No evidence of idempotency, pagination, or composition patterns.

• Rename tools with clear action verbs: 'convert_markdown_to_epub' and 'manage_ideas' (or split idea_refine into 'init_ideas_directory', 'list_ideas', 'add_idea', etc.).
• Add descriptions to all parameters. For markdown_to_epub: 'title' → 'Book title for EPUB metadata (optional; if omitted, extracted from markdown H1). Max 200 chars.' For idea_refine: 'action' → 'Action to perform: init (create ideas directory), list (show all ideas), add (create new idea), remove (delete idea).'
• Document output schemas. E.g., markdown_to_epub returns {success: boolean, epub_path: string, file_size_bytes: number, chapters: number}. idea_refine returns {success: boolean, message: string, ideas_count?: number}.
• Add enum constraints to action parameter in idea_refine. Use JSON Schema enum: ['init', 'list', 'add', 'remove'] instead of free-form string.
• Add error handling guidance in descriptions. E.g., markdown_to_epub: 'If markdown is invalid, returns error with line number. If output_path is not writable, returns permission error, check directory exists and is writable.'