Identify exported symbols never imported by other files and delete them. Use dry_run to preview results before applying changes.
Find exported symbols that are never imported by any other file in the project. dry_run=true (default) reports only; dry_run=false deletes them.
| Name | Required | Description | Default |
|---|---|---|---|
| dry_run | No | If true (default), only report — do not delete | |
| file_pattern | No | Limit analysis to files matching this path substring |
Changes observed during successful MCP inspections.
v1.10.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It transparently states that the default is non-destructive reporting and that dry_run=false deletes the symbols. It could add details about permanence or file modification scope, but it clearly signals the destructive path.
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?
The description is a single well-structured sentence that front-loads the purpose and then clearly states the safety/default behavior and the destructive alternative. 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 tool with two simple, fully documented parameters and no output schema, the description is largely complete: it explains what the tool finds, what it reports by default, and what happens with dry_run=false. It could mention the output format or irreversible side effects, but the core invocation context is present.
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?
Schema description coverage is 100%, so both parameters are already documented. The description reinforces the dry_run semantics but adds no extra meaning beyond the schema, and it does not elaborate on file_pattern behavior.
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?
The description states a specific verb and resource: find exported symbols never imported by other files, with an optional delete action. This clearly differentiates it from sibling tools like search_symbol or read_file_symbol, which locate/read symbols but do not analyze dead code or delete it.
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 description gives clear context: use it to find dead exports, with dry_run=true as the safe default and dry_run=false triggering deletion. It doesn't explicitly name alternatives or exclusions, but the intended usage is unambiguous enough for an agent to select it appropriately.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.