well-008-text-stats

There is only one tool, so there is no possibility of confusion or misselection between tools. Its purpose (fetch text from an HTTPS URL and compute counts plus SHA-256) is stated unambiguously.

The single name 'text-stats' is clear, descriptive, and uses kebab-case with no competing conventions to clash against. It is not a verb_noun pattern like fetch_text_stats, so it is slightly less predictable for an agent inferring naming style.

A single tool is borderline thin under the rubric, which notes 1-2 tools feels sparse. The functionality is narrowly scoped (one URL in, one JSON stats object out), so one tool is defensible, but there is no accompanying variant or helper surface.

For its stated purpose the tool is self-contained: it returns byte/char/line/word counts and a hash, documents caps, redirects, and content-type rejections, and produces a structured JSON result. It lacks options (e.g. hashing without fetching, configurable size caps, or batch URLs), which are minor gaps an agent can work around.