This server has significant definition quality gaps. While tool names follow verb_noun conventions (create_blog_post, optimize_blog_content), descriptions are present but often generic and lack actionable context. Most critically, parameter schemas are visible in code but descriptions are minimal or missing for many parameters. For example, 'style' parameters accept free-form strings instead of enums (should be: professional|casual|academic). Output schemas are not documented, callers cannot predict response structure. Error handling is minimal (generic try/except blocks returning {"error": str(e)}). The server mixes unrelated domains (blog content, guesthouse design, media generation) into one tool set, violating single-responsibility principle. No tool annotations (readOnlyHint, destructiveHint) despite clear WRITE vs READ_ONLY risk classifications.

• Convert all enum-like parameters to JSON Schema enum constraints. Replace 'style: str' with 'style: enum[professional|casual|academic]' in all tools.
• Document output schemas for every tool. Add a 'Returns' section specifying field names, types, and meanings. Example: 'Returns {title: str, content: str, file_path: str, slug: str, frontmatter: str, summary: str, image_suggestions: list[str], estimated_reading_time: int}'.
• Replace generic error handling with actionable messages. Instead of {"error": str(e)}, return {"error": "File not found at /path/to/file. Ensure the path exists and is readable."} with recovery hints.
• Add tool annotations via FastMCP. Mark destructive tools with @mcp.tool(destructiveHint=True) and read-only tools with @mcp.tool(readOnlyHint=True).
• Split into separate MCP servers: blog-content-server (create_blog_post, optimize_blog_content, etc.), guesthouse-server (design_guesthouse_space, etc.), media-server (generate_image, optimize_image, etc.). Each server should have a focused domain.

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

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