Scored across 10 tools
Each tool targets a clearly distinct artifact or diagnostic concern (crash dumps, heap, deadlocks, bytecode decompilation, metadata, assembly diffing, obfuscation, runtime token extraction, IL patching, wrapper generation). Descriptions even include explicit 'Do NOT use X, use Y' cross-references, eliminating plausible confusion between close pairs like inspect_metadata vs extract_tokens or clean_obfuscation vs patch_il.
All tools share the sharphy_ prefix and nearly all follow a verb_noun pattern (analyze_dump, inspect_heap, decompile_method, diff_assemblies, patch_il). The single outlier is sharphy_deadlock_detector, which is noun-based rather than an imperative verb, but it remains readable and predictable.
Ten tools is well within the ideal range and each maps to a distinct reverse-engineering or diagnostics workflow stage. No tool appears redundant or padded.
The surface covers the core lifecycle of dump analysis, static inspection, runtime reflection, diffing, and mutation (patching, obfuscation cleanup, wrapper generation). Minor gaps exist: no live-process attach/inspection, no assembly discovery/enumeration or type-search tool, and no way to execute or invoke a method after patching.