Most tools target distinct resource/action pairs, but there is some overlap among text and structure retrieval tools: lt_get_text, lt_get_edition_text, lt_get_provisions, lt_get_provision, and lt_get_definitions all deal with act content and could be briefly confused. The detailed descriptions generally resolve the boundaries, and reference tools lt_resolve_reference and lt_check_document_references are distinguishable by scope.

All tools use a consistent lt_ prefix and snake_case, with mostly verb_noun patterns such as lt_get_act, lt_search_in_act, and lt_list_amendments. The main deviations are noun-style names lt_coverage and lt_health, which are minor but slightly break the otherwise predictable convention.

At 20 tools this is somewhat above the ideal compact range, but the legal-research domain legitimately requires separate operations for acts, provisions, editions, amendments, attachments, court rulings, references, and health/coverage checks. No tool appears clearly redundant or filler, so the set is slightly heavy but reasonably scoped.

The surface covers core legal retrieval and lifecycle needs: search, act metadata, full text, provision structure, editions, diffs, amendments, attachments, court rulings, citation checks, and connector coverage/health. A notable possible gap is cross-act full-text search, since lt_search appears title-based and lt_search_in_act is limited to a single act, but most workflows are well supported.