Tidy Byte Tools API

Tools generally target distinct resources and actions, and descriptions clarify the borderline cases (json_format vs. json_repair vs. json_shaper handle valid JSON, broken JSON, and non-JSON sources respectively). The main risk cluster is the three JSON tools plus base64/url_codec, which an agent could occasionally misselect without reading descriptions carefully.

Consistent lowercase snake_case throughout, mostly following a subject_action pattern (cron_parse, id_generate, html_sanitize, unit_convert, json_repair). Minor deviation: a few tools are bare subjects (base64, hash, unicode) and some second tokens are nouns rather than verbs (gtin_checksum, url_codec, text_diff), but the pattern is still readable.

19 tools is on the heavy edge but defensible for a general developer-utility toolkit, since each tool covers a distinct encoding, format, or conversion domain. Nothing appears obviously redundant or padding.

Covers a broad, coherent set of byte/text utilities: encoding (base64, url_codec, hash), structured data (json_*, xml_json, yaml_json, sql_format), and text transforms (unicode, text_diff, md_chunk). Minor gaps exist, such as no reverse MD-chunking/JSON-to-CSV output and no JWT verification or regex/escape utilities, but core workflows are all reachable.