well-002-url-to-markdown

There is only one tool, so there is no possibility of misselection. Its purpose (fetch a public https URL and return markdown) is stated precisely, including scope limits and return shape.

A single kebab-case name that clearly describes the input-to-output transformation. With one tool there are no competing conventions to clash, and the name is self-explanatory.

The server is intentionally atomic, so one tool is defensible, but by general standards a 1-tool surface is thin and leaves no room for related operations (batch fetch, HTML/text conversion, capability/health check).

For the narrow url-to-markdown domain, the surface is essentially complete: it handles redirects, content-type, title, and warnings, and documents failure modes. Minor gaps exist (no bulk conversion, no options for output shaping), but the core operation has no dead ends.