Accuracy is the foundation of trust. At Tool-web, we are committed to verifying every factual claim we publish. This page explains the rigorous fact-checking process that underpins all of our content.
Our Fact-Checking Principles
- ✓Verify Before Publishing — No factual claim is published until it has been independently verified against a reliable source.
- ✓Primary Over Secondary — We always prefer primary sources (official documentation, specifications) over secondary sources (blog posts, articles).
- ✓Test, Don't Assume — When verifying tool capabilities or outputs, we test directly rather than relying on documentation alone.
- ✓Cite Our Sources — We provide links to our sources wherever possible so readers can verify claims independently.
- ✓Acknowledge Uncertainty — When a claim cannot be fully verified, we say so explicitly rather than presenting it as established fact.
Source Hierarchy
We categorize sources into three tiers based on reliability. Higher-tier sources are preferred, and a claim must be supported by at least one source from Tier 1 or Tier 2.
Primary Sources
Official documentation, specification bodies (W3C, ECMA, IETF), manufacturer datasheets, and official API references. These are our highest-trusted sources and are used whenever available.
Examples: MDN Web Docs, W3C specifications, official tool documentation, government datasets
Secondary Sources
Peer-reviewed research, established industry publications, and well-documented open-source projects with active maintainers. These are used when primary sources do not directly address a claim.
Examples: IEEE publications, GitHub repositories with active maintenance, established tech publications
Tertiary Sources
Community knowledge bases, Stack Overflow answers with high community validation, and reputable tutorials. These are used for supplementary context but never as the sole source for a factual claim.
Examples: Stack Overflow (high vote answers), community wikis, reputable tutorial sites
How We Verify Tool Claims
Tool descriptions are one of the most critical areas for fact-checking. Users rely on our descriptions to understand what a tool does and whether it meets their needs.
- Feature Verification — Every listed feature is tested directly in the tool. If we say a tool can do something, we have verified it works.
- Output Validation — Tool outputs are compared against known correct results. For calculators, we verify against established formulas. For converters, we check against reference implementations.
- Limitation Disclosure — We test edge cases and document limitations. If a tool has known limitations, we state them clearly.
- Comparison Accuracy — When we compare tools or features, the comparisons must be fair, documented, and based on identical test conditions.
Data Accuracy Standards
When our content includes data, statistics, or numerical claims, we apply these standards:
- ✓Recency — Data must be from a recent source. We prefer data less than 2 years old and note when older data is used.
- ✓Methodology Transparency — When citing statistics, we note the source methodology so readers can assess reliability.
- ✓Context — Numbers are presented with appropriate context. We avoid cherry-picking data points that support a predetermined narrative.
- ✓Rounding — When rounding numbers, we use standard rounding rules and note the original precision where relevant.
Handling Disputed Claims
When a claim is disputed or when multiple credible sources disagree, we take a careful approach:
- ✓We present the consensus view as the primary position.
- ✓We note when there is meaningful disagreement among experts.
- ✓We link to multiple sources so readers can form their own conclusions.
- ✓We update our position when new evidence emerges.
Contact Us
If you believe we have published inaccurate information, please contact us through our contact page or email support@tool-web.online. We investigate all accuracy claims within 48 hours.