Each tool targets a distinct output type: charts for numeric data, cards for structured info, HTML for free-form interfaces. The descriptions explicitly establish a priority order (render_html is 'FALLBACK ONLY'), which resolves the inherent overlap created by render_html being a superset capability. Minor residual ambiguity remains since an agent could technically render a chart or card via HTML, but the guidance is strong enough to steer selection.

All three tools follow the exact same verb_noun pattern: render_chart, render_card, render_html. The shared 'render_' prefix makes the family relationship obvious and the noun cleanly signals the output target.

Three tools is well-scoped for a UI-rendering server: one per major output modality, with HTML acting as the general-purpose catch-all. No tool feels redundant, and the set avoids both the thinness of a single trivial renderer and the bloat of per-widget tool proliferation.

The surface covers the main inline-rendering needs (data visualization, structured info, arbitrary interactive content), and render_html provides an escape hatch for anything else. Some obvious convenience types are absent—e.g. dedicated table, image/media, or form renderers—but these can be worked around through render_card or render_html, so gaps are minor rather than blocking.