get_conventions retrieves content while list_scopes enumerates available fragment names; the two purposes are clearly disjoint and cannot be confused. Descriptions reinforce the distinction (one returns markdown, the other a list of names).

Both tools follow a consistent verb_noun snake_case pattern (get_conventions, list_scopes). The verbs also match expected semantics — 'get' for retrieval of content, 'list' for enumeration.

Only two tools, which sits at the thin end of the rubric's acceptable range. The domain is narrow (loading convention fragments), so two tools are defensible, but the surface feels minimal even for that scope.

The read-only retrieval lifecycle is essentially covered: discover scopes, then fetch a fragment (default or scoped) in one call. Minor gaps exist around verifying fragment freshness or version, but agents can work around them by re-calling get_conventions.