move_path

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

The description only states the basic action without disclosing behavioral traits. It fails to mention whether the operation overwrites existing destinations, what happens on partial failure, atomicity, or permission requirements. Since no annotations exist, the description carries the full burden but provides almost no behavioral context.

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 extremely concise (one sentence) and front-loaded, but it sacrifices necessary detail. While there is no fluff, the brevity reduces its value. It could have included key behavioral notes without becoming verbose.

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?

Given the complexity of a move/rename operation (including potential overwrite, cross-workspace moves, and error handling), the description is incomplete. No output schema is provided, and annotations are absent, so the description should compensate but fails to address conflict resolution or operation boundaries.

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 input schema has 100% description coverage, with each parameter having a brief description (e.g., 'Source path'). The tool description adds no additional meaning beyond what the schema already provides, so the baseline score of 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?

The description explicitly states 'Move or rename a file or directory', which clearly identifies the action and resource type. It distinguishes the tool from siblings like create_directory, delete_path, and edit_file, as no other sibling handles move/rename.

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?

No guidance is provided on when to use this tool vs alternatives. There is no mention of prerequisites, restrictions, or situations where another tool (e.g., copy then delete, or using write_file) might be more appropriate.

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