Single tool 'convert_html_to_asset' has a comprehensive schema with 14 parameters, all properly typed with min/max constraints and enum values. Description is detailed (340+ chars) and explains use cases. However, output schema is not documented, LLMs cannot predict return structure. Parameter descriptions are present but some lack actionable format guidance (e.g., 'output' param says 'must be inside OUTPUT_DIR' but doesn't explain the directory structure or how to discover it). Error handling is not visible in the tool definition. Tool name is clear and verb-prefixed ('convert_'). No security concerns visible (no secrets in params). Composition is single-purpose, appropriate for the domain.

• Document the output schema explicitly: 'Returns an object with fields: file_path (string, absolute path to output file), width (number), height (number), format (string), duration_ms (number, only for animated formats), error (string, null if successful).'
• Clarify OUTPUT_DIR in the 'output' parameter description: 'Custom output file path. Must be an absolute path within the server's configured OUTPUT_DIR (default: /tmp/pixdom-output). If omitted, a timestamped filename is auto-generated.'
• Add error handling guidance to the tool description: 'Returns error details if rendering fails (e.g., invalid HTML, timeout after 30s, unsupported format). Retry with simpler HTML or smaller dimensions if timeout occurs.'
• Formalize mutually exclusive parameters in the description: 'Exactly one of html, url, file, or image must be provided. Passing multiple inputs will result in an error.'
• Enhance 'selector' parameter: 'CSS selector to capture a specific DOM element (e.g., "#card", ".hero", "div.container > p:first-child"). Must be valid CSS3 selector syntax. If element not found, returns error.'
• Add a 'profile' parameter note: 'Platform preset overrides width/height. If both profile and width/height are provided, profile takes precedence.'