remove_import

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. Description explains matching logic but does not mention side effects (file modification), error behavior, permissions, or return values. Critical behavioral aspects are missing.

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?

Concise: a few sentences covering purpose, usage guidelines, and an example. No redundant information. Front-loaded with the main action.

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?

Low parameter count and has output schema. Description covers purpose and usage but lacks behavioral details like modification effects, error handling, or return type. Adequate but with gaps.

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 has 0% description coverage. Description adds meaning: file_path is the source file, import_text is the exact line (stripped). Example clarifies format. However, it omits file_path constraints (e.g., relative/absolute path).

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 clearly states the action (remove), resource (import statement), and context (from source file). It also explains matching logic and differentiates from remove_import_name, which is a sibling tool.

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?

Explicitly states when to use (remove unused import) and when not to use (remove one name from multi-name import), including the alternative tool name remove_import_name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.