The server has 5 tools with significant definition gaps. Most descriptions are present but generic/incomplete. Input schemas are partially defined, some parameters lack types or descriptions. Tools lack error handling guidance, and output structures are not formally documented. This is a typical community-grade implementation with room for improvement in LLM usability.

• Rename 'select_image_regions_tool' → 'select_image_regions' and 'get_working_directory_tool' → 'get_working_directory' to remove '_tool' suffix for consistency with other tools.
• Expand descriptions to 50 - 200 characters for simple tools (get_server_version, get_recipe_prompt) explaining not just WHAT but WHEN/WHY to call them. E.g., 'get_server_version: Retrieve the MCP server version for compatibility checks or debugging. Returns a semantic version string (e.g., 0.9.2).'
• Add per-parameter descriptions to 'build_recipe_html_tool'. Document each parameter's purpose, format, and constraints. E.g., 'prep_time: Preparation duration in natural language format (e.g., "15 Min", "1 Std"). If omitted, field is hidden in output.'
• Document output schemas for all tools in descriptions or via structured response examples. E.g., 'build_recipe_html_tool returns a JSON object with {filepath: string, recipe_name: string, status: 'success'|'error'}'.
• Add error handling guidance: For 'select_image_regions_tool', clarify what happens if image_path is invalid (e.g., 'Returns error: "Image not found at <path>. Available images in <working_dir>: [list]". Try again with a valid path or call get_working_directory_tool().').
• Add format constraints to time parameters in 'build_recipe_html_tool'. E.g., 'prep_time: Time in German format (e.g., "15 Min", "1.5 Std"). Must match pattern /^\d+(\.5)?\s(Min|Std)$/ or will cause template errors.'
• Translate all descriptions to English (or provide English alongside German) for global LLM compatibility. MCP is language-agnostic but LLMs default to English reasoning.