Scored across 7 tools
Most tools target clearly distinct questions: architecture map, module profile, blast radius, function search, dead code, account. The only real overlap is pharaoh_recon, which bundles codebase map, module profiles, searches, and blast radius, so an agent might hesitate between it and the individual tools. The descriptions do mitigate this with explicit 'call this when' guidance, but the batch wrapper is inherently a superset of other tools.
Mostly consistent snake_case with a verb-first pattern (get_codebase_map, get_module_context, get_blast_radius, search_functions, get_unused_code). The two pharaoh_-prefixed tools (pharaoh_recon, pharaoh_account) break the verb_noun convention slightly, but remain readable and logically clustered as server-management operations.
Seven tools is well-scoped for a codebase-intelligence server, and each tool earns its place: map, module context, impact analysis, function search, dead-code detection, batch recon, and account management. No padding or obviously trivial tool.
Coverage is strong for architecture understanding, change impact, function discovery, and unused-code cleanup. The notable gap is that none of the tools return actual source code bodies or line contents—agents can locate and assess functions but cannot read the implementation, which may force a fallback to another file-access mechanism.
