organize_imports

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

Discloses that it returns the organized import block for replacement rather than modifying the file directly. Also notes the load_project dependency. Lacks details on error handling or side effects, but adequate for this mutation tool.

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?

Description is brief and front-loaded with the core action. The usage example is placed after the explanation, no wasted words.

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?

Covers purpose, prerequisite, and return value. Does not detail output structure beyond 'list of changes', but for a simple tool with no output schema, this is sufficient.

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 only parameter 'filePath' is documented in schema as 'Path to source file'. The description adds a usage example but no deeper semantics. Schema coverage is 100%, baseline 3 is appropriate.

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?

Description clearly states the tool organizes imports in a Java file by removing unused and sorting alphabetically, with a specific return object. This distinguishes it from siblings like suggest_imports or find_unused_code.

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?

Specifies prerequisite (load_project) and gives example usage. It does not explicitly contrast with other import tools, but the single-purpose design makes appropriate use clear.

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