Vairiant: 152-FZ website check

The three tools have clearly distinct roles: check_site performs the compliance check, create_checkout generates a payment page link from a check_id, and get_offer provides product/pricing information. Their workflow dependency is explicit, so an agent can easily choose the right tool.

All tools follow a consistent snake_case verb_noun pattern: check_site, create_checkout, get_offer. There are no mixed conventions or vague names.

Three tools are well-scoped for this narrow domain: discover the offer, check the site, and create a checkout link. Each tool earns its place, and there is no redundant surface.

The surface covers the main lifecycle: get_offer for product/pricing, check_site for compliance findings and check_id, and create_checkout for handing payment to the human. A minor gap is the lack of a standalone way to retrieve or re-check a prior check result by check_id, though check_site returns the needed data initially.