e18e

Each tool has a distinct purpose: one checks source code for inefficient imports, one looks up replacements by various criteria, and one checks install command syntax for outdated packages. There is minor overlap between code-checker and npm-i-checker, but descriptions clarify the different contexts, so agents can generally distinguish them.

All use snake_case, but the naming patterns are inconsistent: 'code-checker' and 'npm-i-checker' follow a noun-checker pattern, while 'lookup-replacement' uses a verb-noun pattern. 'npm-i-checker' is also somewhat cryptic, mixing package manager syntax. This lack of a uniform verb_noun convention makes the set less predictable.

With 3 tools, the server is well-scoped for its purpose of checking code and packages for inefficient or outdated dependencies. Each tool addresses a distinct aspect of the workflow, and there are no redundant or missing tools that would make the count feel too thin or heavy.

The tool surface covers the main needs: checking source code, looking up replacements generally, and verifying install commands. A minor gap is the lack of a direct tool to check a package.json file or to analyze a whole project for inefficiencies, but the three tools together handle most common scenarios without significant dead ends.