Single tool with complete input schema and reasonable description. Naming follows verb_noun pattern (convert_html_to_pdf). Schema includes 15 parameters with types and descriptions. However, output schema is not documented, LLMs cannot predict response structure. Parameter descriptions lack actionable constraints (e.g., scale range 0.1-2 stated in description but not enforced in schema). No error handling guidance. Missing required/optional field declarations in schema.

• Add explicit output schema documentation: { success: boolean, message: string, outputPath: string, processingTime: string, fileSize: string }. Include in tool definition or response handler comments.
• Add 'required' array to inputSchema: ['htmlPath' OR 'htmlContent'], document that exactly one must be provided. Consider splitting into two tools (convert_html_file, convert_html_string) to eliminate ambiguity.
• Enhance error messages with recovery guidance: 'File not found at {path}. Check path is absolute or relative to cwd.' 'Timeout after {timeout}ms. Increase timeout parameter or simplify HTML.' 'Invalid format: got {format}, must be one of: A4, A3, Letter, Legal, Tabloid.'
• Add JSON Schema constraints: scale { type: 'number', minimum: 0.1, maximum: 2 }, timeout { type: 'number', minimum: 1000, maximum: 300000 }, margins with pattern for units.
• Document parameter dependencies in descriptions: 'headerTemplate and footerTemplate only apply if displayHeaderFooter is true.' Add oneOf or if-then-else schema validation if possible.