Three tools with clear verb-noun naming (generate_chart, render_option, list_chart_types). Descriptions present but generic (50-100 chars, below 194-char baseline). Input schemas visible with type definitions, but parameter descriptions are sparse and lack actionable constraints. generate_chart has 7 params but only 2-3 have meaningful guidance; render_option similar. No output schemas documented. Error handling not visible in tool definitions. Missing enum constraints for 'output' and 'theme' parameters despite known valid values.

• Convert 'output', 'theme', 'delivery', and 'type' parameters to enums in JSON Schema. Replace string descriptions like 'svg, png, option, or html' with formal enum constraints.
• Expand tool descriptions to 150-250 chars. For generate_chart: 'Generate a chart from a built-in template. Use this when you have data and want a quick, styled chart. Returns SVG/PNG/HTML/option object based on output param.' For render_option: 'Render a custom ECharts option object. Use this when you have full control over the chart config. Returns SVG/PNG/HTML.'
• Document output schemas. E.g., generate_chart returns {success: bool, output: string (file path or base64), format: string, size: {width, height}}. render_option returns {success: bool, output: string, format: string}.
• Add parameter descriptions for 'delivery': 'Where to send the output: file (saved to disk, returns path), base64 (embedded in response), or html (standalone HTML document).'
• Add dependency hints in descriptions. E.g., 'Call list_chart_types first to see available chart types and their data structure requirements.'