caddy-mcp has 7 tools with clear verb-noun naming (get_, list_, validate_, adapt_, load_, patch_, stop_). All tools have descriptions (avg 95 chars, within 10-1024 range). However, input schemas lack parameter descriptions for most tools, only 'caddyfile' and 'path' have descriptions; 'config', 'value', and boolean flags lack them. Output schemas are undocumented. Error handling is minimal: no recovery guidance, no categorization of retryable vs fatal errors. Dry-run defaults are good for safety, but destructive operations (stop_caddy, load_config, patch_config) lack confirmation patterns beyond dry_run. No tool annotations (readOnlyHint, destructiveHint) present.

• Add descriptions to all parameters: 'config' (JSON object to load into Caddy), 'value' (new value to set at path), 'dry_run' (if true, preview operation without executing). Use the pattern: 'The <param> (type, constraints, e.g. ...).'
• Document output schemas for each tool. E.g., get_config returns {apps: {http: {servers: {...}}, ...}, ...}; validate_caddyfile returns {valid: bool, stdout: str, stderr: str, returncode: int}. Include this in docstrings or a separate schema file.
• Add tool annotations to FastMCP tool decorators: @mcp.tool(annotations={'readOnlyHint': True}) for get_config, list_reverse_proxy_upstreams, validate_caddyfile_text; @mcp.tool(annotations={'destructiveHint': True}) for stop_caddy; @mcp.tool(annotations={'destructiveHint': True, 'idempotentHint': False}) for load_config and patch_config.
• Enhance error messages with recovery guidance. Instead of 'Caddy admin API PATCH /config/apps/http failed with 400. Response body redacted.', return 'Failed to patch config: invalid JSON structure. Verify the value matches Caddy's schema. Try validate_caddyfile_text() first to check syntax.'
• Add per-item error handling for batch operations. If list_reverse_proxy_upstreams fails to parse a server, return partial results with error details rather than failing entirely.