validate and render are mostly distinct (one checks, one draws), but both return located violations, so an agent could plausibly reach for render while drafting and lose the stated benefit of validate. kinds is clearly separate as the vocabulary lookup. The boundary is workable but not perfectly crisp.

All three names are single lowercase tokens with no style mixing (no camelCase/snake_case clash), which is predictable. However, the set mixes parts of speech—two imperative verbs (validate, render) and one bare noun (kinds)—so it is not a true verb_noun convention.

Three tools is on the lean side but each earns its place: validate for pre-flight checks, render for output, kinds for discovery. For a focused document-to-SVG service this is well-scoped rather than padded or thin.

The core lifecycle—learn the vocabulary (kinds), check the document (validate), produce output (render)—is fully covered, and documents live outside the server so CRUD is unnecessary. Minor gaps remain, such as no way to introspect the full document schema beyond the kind vocabulary or to fetch worked examples.