Lazynext Accessibility Checker

Each tool targets a clearly distinct action: get_report retrieves a stored result, list_rules enumerates WCAG criteria, scan_html audits static markup, and scan_url renders and audits a live page. The static-vs-render distinction between the two scan tools is explicitly documented, so an agent can select correctly.

All four tools follow a strict verb_noun snake_case pattern (get_report, list_rules, scan_html, scan_url), with no mixed conventions or vague verbs.

Four tools is well-scoped and each earns its place for a focused scanning service, though the surface is small enough that it sits just short of generous. Nothing is redundant or missing-by-count.

The core lifecycle (scan HTML, scan URL, retrieve report, enumerate rules) is covered, but there is no way to list prior reports or check quota/account status, which agents may need after producing a report id.