Scored across 9 tools
Most tools target clearly distinct resources, and descriptions actively cross-reference alternatives (e.g. search_problems vs get_problem, get_problem vs get_daily_challenge). The only real overlap is get_recent_submissions vs get_recent_ac_submissions, which differ narrowly (failed attempts, Global-only), though the descriptions do disambiguate them.
Every tool follows a consistent snake_case verb_noun pattern (get_, search_, list_). No mixing of conventions, and names map cleanly to their actions and resources.
Nine tools is well-scoped for a read-only LeetCode data client, with each tool covering a distinct resource. No filler or redundant tools bloat the surface.
The read-only domain is mostly covered (problems, solutions, users, submissions, contest ranking), but descriptions reference tools that do not exist in the set—get_user_status and get_all_submissions—creating dead ends. There is also no submission/write capability, so any workflow requiring those referenced operations will fail.