Tool Accuracy Policy

Every published tool on Tool Magic Lab is bound to a real handler in the tool engine, and the registry is validated automatically: the build fails if a tool points at a handler that does not exist, has a duplicate slug, or lacks its content fields. Engine functions are covered by automated tests, including known-answer tests (for example, the MD5 implementation is verified against the RFC 1321 test vectors, and unit converters against exact defined factors).

Calculators display their formulas or assumptions and use editable rate fields wherever a fee, tax or price schedule can change. A calculator is a model: its result is exactly as accurate as the rates and inputs you give it, and it is not a substitute for your own account statements, contracts or professional advice.

Converters that depend on live data show their source and timestamp — exchange rates name the provider and the rate date; time-zone conversions use the IANA database including daylight-saving rules. When a live source is unreachable, the tool says so and offers a manual mode rather than inventing a number.

Tools that run in your browser process your files and text on your device. Tools that need a server or a third-party API say so on their page. AI tools generate nothing at all until a real model provider is configured by the site administrator.