Scored across 28 tools
Most tools are clearly scoped to distinct operations (replace body vs. replace signature vs. replace whole function), and the descriptions include explicit 'Don't use this when' guidance. However, the large number of overlapping edit tools (replace_function, replace_function_body, replace_in_body, replace_signature, add_parameter, remove_parameter) could still cause an agent to pause and choose carefully, especially with insert_in_body vs. insert_sibling vs. add_top_level.
The naming pattern is mostly consistent verb_noun (replace_function, replace_signature, add_import, remove_import, delete_key, add_key, list_symbols, read_symbol). Minor deviations exist: 'edit_leading_comment' uses 'edit' instead of 'replace'/'update', and 'insert_sibling' uses 'insert' while the body-level tool is 'insert_in_body' — but the pattern is still predictable and readable.
28 tools is on the heavy side for a code-editing server, though each tool targets a fairly specific operation. The count is justified by the breadth of languages and file types supported, but it approaches the threshold where an agent may struggle to select among many similar edit operations.
The tool surface covers the full lifecycle of code editing: reading structure (list_symbols, read_symbol, read_imports, find_references), adding/removing/replacing functions, methods, fields, imports, parameters, docstrings, comments, and config values. The only minor gap is the absence of a dedicated 'rename symbol' tool, but that can be composed from replace_signature and replace_in_body/find_references.