Sort and combine imports in TypeScript/JavaScript files, and remove unused ones. Applies changes directly to disk to keep code clean.
Sort imports and remove unused ones in a TypeScript/JavaScript file. Applies the changes to disk.
| Name | Required | Description | Default |
|---|---|---|---|
| file | Yes | Relative file path from project root | |
| skipDestructiveCodeActions | No | Only sort and combine imports, without removing unused ones |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Explicitly discloses that changes are applied to disk, a critical side effect, and states that unused imports are removed. With no annotations, this is meaningful behavioral disclosure, though it omits details like reversibility or safety precautions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler, front-loading the core purpose and then the key side effect. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter mutation tool with a complete schema, the description covers the essential operation and its disk-writing behavior. It would benefit from routing guidance versus siblings, but nothing critical is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes both parameters at 100% coverage, including the meaning of skipDestructiveCodeActions. The description adds no additional parameter-level detail, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: sorts and removes unused imports in a TypeScript/JavaScript file. The operation is clearly distinct from siblings like format or code_actions, though it does not explicitly name an alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The use-case is implied by the purpose, but there is no explicit guidance on when to choose this tool over format or generic code_actions. No exclusions or alternative conditions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.