well-004-html-to-markdown

With only one tool, there is zero possibility of misselection or overlap. The tool's purpose (HTML → Markdown conversion) is unambiguous and fully spelled out.

The single kebab-case name 'html-to-markdown' is descriptive and follows a clear convention. There is no competing style to conflict with, so consistency is trivially satisfied.

For a narrowly scoped conversion microservice, one tool is the right surface — bundling unrelated operations would add noise. It sits at the low end of the typical range, but the scope genuinely is a single operation.

The tool covers both input paths (raw html string or fetched url), documents limits, and returns markdown plus warnings, which is full lifecycle for this domain. Minor gaps like batch input or format/output-shaping options are absent but not essential.