Each tool has a reasonably distinct role: list_topics is an index, get_questions is filtered retrieval, get_answer_framework is single-question deep dive, random_drill is a timed mock, and search_questions is keyword lookup. The only real overlap is between get_questions and search_questions (both return question lists) and between random_drill and get_questions (both sample questions), but the descriptions make the intent differences clear.

Four of five names follow a clean verb_noun pattern (list_topics, get_questions, get_answer_framework, search_questions). random_drill breaks the pattern as an adjective+noun with no verb, though it is still readable and unambiguous.

Five tools is well-scoped for a question-bank server: discover, retrieve, drill, deep-dive, and search. Each tool earns its place with no redundancy padding the surface.

The core read lifecycle is covered: topic discovery, filtered retrieval, answer frameworks with rubrics, random drilling, and search. Minor gaps exist — no single-question fetch by id independent of the answer framework, and no attempt/progress tracking across drill sessions — but agents can work around both.