Move or rename

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

No annotations are supplied, so the description carries the full behavioral burden and delivers almost none of it. It does not say what happens when the destination already exists and overwrite is false, that overwriting irreversibly destroys the existing file/folder, whether missing parent directories are created, or whether the operation works across roots. For a destructive-by-nature mutation with zero annotation coverage, this is a serious gap.

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?

A single front-loaded sentence with zero filler and the core verb immediately visible. Its brevity is efficient rather than padded, though it tips into under-specification rather than choosing its words carefully.

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?

For a mutating filesystem tool with three parameters, no annotations, and no output schema, the description omits everything an agent needs to call it safely: overwrite risk, failure conditions, and whether the destination path is created or must exist. The schema covers parameter shapes but not consequences.

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%, so the schema already documents all three parameters including the overwrite default of false. The description adds only indirect meaning via the word "renames," clarifying that destination may name an existing directory or a new name; it adds no detail on path format (absolute vs. relative, root prefix) beyond what the schema provides. 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?

"Moves or renames a file or folder" gives a specific verb pair and resource, and the rename clause usefully implies same-location source→destination semantics. It does not distinguish itself from siblings such as copy_path or restore_path, which is the only thing keeping it out of a 5.

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?

There is no when-to-use guidance at all: no statement of when to prefer this over copy_path plus delete_path, no mention that restore_path or undo_last_change is the route for reverting. The one branching decision in the tool — the overwrite flag — is never explained in terms of when an agent should set it.

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