One clear job
Each tool starts with a repeatable problem that can be explained in one sentence. The interface should make the common path obvious without hiding the decisions that affect the result.
Privacy stated precisely
“Private” is not used as a vague promise. A tool explains whether input stays in the browser, reaches an API, is stored, or is visible to a separate advertising provider.
Limits are part of the documentation
A useful tool says what it cannot do. Image cleanup is not background segmentation. Form encoding is not typed JSON. Clear boundaries help people choose the right method before trusting an output.
Maintained as software
The tools use automated tests, production builds, crawlable documentation, and explicit versioned interfaces where automation is supported. Updates should improve behavior without inventing compatibility claims.