chartgen has 6 tools with basic schemas and descriptions, but significant gaps prevent higher scores. Tool names follow verb_noun convention (generate_chart, list_indicators, add_alert, etc.), which is good. However, descriptions are inconsistent in depth and parameter documentation is sparse. The generate_chart tool has a complex indicators array parameter with minimal schema detail ('items': {'type': 'object'} with no properties defined). Several tools lack parameter descriptions entirely (list_indicators, list_alerts, poll_notifications have empty properties). Error handling is declared but not visible in the source. Output schemas are not documented. The server supports both STDIO and HTTP, but tool definitions appear inferred from file references rather than explicitly visible in registration code.

• Define indicators parameter as an array of objects with explicit schema: each object should have 'name' (enum of supported indicators) and 'parameters' (object with indicator-specific fields). Document in generate_chart description which indicators are available.
• Replace condition parameter in add_alert with discriminated union: define separate fields for price_above_value, price_below_value, and indicator_crossover_config, or use a oneOf schema with explicit condition types.
• Add output schemas to all tools. For generate_chart, document that it returns {image_base64, width, height, ticker, timeframe}. For list_indicators, document the structure of each indicator object.
• Add parameter descriptions to list_indicators, list_alerts, and poll_notifications even if they have no parameters, explicitly state 'This tool accepts no parameters' to clarify intent.
• Document error responses: what happens if ticker is invalid? If alert_id does not exist? Provide recovery guidance (e.g., 'Call list_alerts() to see valid alert IDs').