Reclypse Utility Node

chunk_document and clean_and_chunk overlap heavily, since the latter is essentially the former plus clean_markdown, so an agent may hesitate over which to call. clean_markdown and sanitize_text also both perform text normalization and are only separated by nuance (HTML artifact extraction vs. Unicode/control-noise and instruction-pattern flags). The descriptions do provide enough detail to resolve most choices, but boundaries are not crisp.

All names are snake_case with a leading verb (chunk_document, clean_markdown, sanitize_text, structure_json), which is predictable. The only deviation is the compound clean_and_chunk, which breaks the verb_noun shape but is still readable and self-describing.

Five tools is a tight, well-scoped set for a document/text utility node. The only redundancy is clean_and_chunk acting as a convenience wrapper, but nothing feels padded or missing at this scale.

The surface covers the core pipeline: clean HTML/markdown, sanitize text, chunk documents, and parse JSON, plus a compound shortcut. Minor gaps exist (e.g., no token/count estimation despite chunk limits being described in code points, no reverse markdown/HTML conversion), but agents can work around these.