The docs_search/docs_read pair is clearly distinguished by action, but infomaniak_catalogue and infomaniak_search largely overlap — both describe discovering/browsing public API metadata and operations, and their descriptions even cross-reference the same catalogue. An agent could plausibly pick either for API discovery, though the docs-vs-live capability split is somewhat explained in the text.

All names use the same infomaniak_ prefix and snake_case, with a recognizable docs_search/docs_read and search/read pairing. Minor deviation: some suffixes are verbs (search, read) while others are nouns (catalogue, status), which slightly breaks the verb_noun expectation.

Six tools is well-scoped for a documentation-discovery plus read-execution server, and each maps to a plausible step (search, browse, read docs, execute read, check status). Slightly thin — one redundant discovery tool means the effective distinct surface is closer to five.

The surface covers discovery, documentation retrieval, capability introspection, and read execution, but has no write/create/update/delete operations at all, so any mutation workflow dead-ends. The read-only scope appears intentional and is documented as a policy boundary, which mitigates but does not eliminate the gap for an API-access server.