move_file

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

No annotations are provided, so the description must fully convey behavioral traits. 'Move or rename' implies mutation but does not disclose whether the tool overwrites existing files, requires specific permissions, or is reversible. This is insufficient for a potentially destructive operation.

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, clear sentence with no extraneous words. However, it might be too brief for a file operation that could benefit from additional context. It earns high marks for efficiency but not perfect because it omits useful details.

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?

With no output schema, no annotations, and a simple two-parameter schema, the description should provide more context about return values, error conditions, and behavior (e.g., overwrite, move vs. copy). The current description is minimal and leaves the agent with unanswered questions.

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 coverage is 100%, with both 'source' and 'destination' already described in the schema. The description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate. No extra context like path formats or overwrite behavior is provided.

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 'Move or rename a file' clearly states the action (move/rename) and resource (file), with a specific verb and object. It distinguishes itself from sibling tools like read_file, write_file, and compress_files, which perform different operations.

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 on when to use this tool versus alternatives such as copy_file or rename operations. The description does not mention any prerequisites, scenarios, or limitations, leaving the agent without context for selection.

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