move_file

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. However, it merely repeats the schema description and adds no unique behavioral details about overwrite behavior, permissions, or error handling. It only mentions the file-only restriction, which is already in the schema, offering no additional insight.

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 English portion is concise and front-loaded, but the description duplicates the entire content in Chinese and includes repetitive keywords, making it longer than necessary. The redundancy reduces efficiency, though the core message is still clear.

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?

The description covers the basic operation and file-only restriction, and an output schema exists, so return values are addressed. However, with no annotations, it lacks crucial context about overwrite behavior, path resolution, and error handling, leaving gaps for a mutation tool. It is minimally complete but not thorough.

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 full descriptions for both source and destination (100% coverage), so the baseline is 3. The description itself adds no extra meaning beyond the schema; it only restates the file-only constraint and path types without elaborating on format, resolution, or edge cases.

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 'Move or rename specific file' with the explicit scope 'Only works on files, not directories', which distinguishes it from the sibling 'move' tool. It also provides a specific verb and resource, making the purpose unambiguous.

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 explicitly says 'Use 'move' tool if unsure about path type,' providing a clear alternative and when to use it. It also clarifies that directories are not supported, giving an explicit when-not-to-use signal. This is strong usage guidance.

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