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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description does not need to restate that the operation modifies state. However, it adds no extra behavioral context beyond the action, such as the effect on the source path or the overwrite option's consequences. Since annotations cover the destructive nature, a neutral score of 3 is appropriate.

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, direct sentence that front-loads the core action. It contains no redundant words or unnecessary detail, making it optimally concise and easy to parse quickly.

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 schema covers parameter semantics and an output schema exists, so return values are not required in the description. However, the description lacks any guidance on when to use this tool or potential edge cases, such as moving directories or overwrite behavior. Given the tool's simplicity and rich schema, a score of 3 reflects that it is adequate but not fully comprehensive.

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 provides comprehensive descriptions for all four parameters, including path syntax and the overwrite flag, achieving 100% coverage. The tool description adds no parameter-specific information beyond what the schema already documents, so it adds no extra value beyond the baseline.

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 tool's action: moving or renaming a file or folder. It specifies both the verb (move/rename) and the resource (file/folder), which distinguishes it from siblings like delete_path or write_file. The title 'Move or rename' reinforces the purpose without ambiguity.

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 versus alternatives. It does not mention scenarios like relocating files vs. copying, or when to use delete_path for removal. The description offers no context on prerequisites or comparisons with sibling tools, leaving the agent to infer usage from the name alone.

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