Each tool targets a distinct resource or session action: auth trio (iec_login/iec_session_status/iec_logout), customer, contracts, bills, invoices, PDF, meters, readings, and consumption are clearly separated. The only mild proximity is get_electric_bill vs list_invoices, but the descriptions frame one as a current summary and the other as a per-period invoice list, which is enough to choose correctly.

The dominant pattern is a consistent verb_noun snake_case (get_customer, list_contracts, get_invoice_pdf, etc.), which reads predictably. The deviation is the iec_ prefix reserved for the three session/auth tools, a minor but noticeable inconsistency rather than a readability problem.

Eleven tools is well within the ideal range and each one maps to a concrete self-service need (auth, account lookup, contracts, billing, invoices, metering, consumption). Nothing feels redundant or padded; the surface is scoped to a single utility-customer domain.

Coverage spans the full read lifecycle of an electricity account plus session management and an invoice download, so common agent workflows have no dead ends. Minor gaps remain around write/action operations (payments, contract or tariff detail beyond the summary) that an agent might expect for a customer portal.