Move or rename Nextcloud file

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

Annotations already indicate destructiveHint=true, so the description doesn't need to restate that. However, it adds the constraint 'inside the configured root,' which is useful context. It does not disclose other behavioral traits like overwrite semantics or conflict handling, but given the annotation coverage, this is acceptable.

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 sentence, front-loaded with the verb and object. It is concise with zero wasted words, fully fitting the tool's simple purpose.

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 an output schema present, the description need not explain return values. The tool is straightforward, and the root constraint is mentioned. However, the lack of parameter semantics and overwrite behavior leaves some gaps. It is adequate but not 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?

Schema description coverage is 0%, so the description must compensate for parameter meaning. It does not mention source, destination, or overwrite at all. The action implies that source and destination are paths, but no details are given about format, overwrite behavior, or defaults, leaving the agent to infer from schema field names alone.

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 states a clear action: 'Move or rename a file/folder inside the configured root.' It specifies the resource (file/folder) and the operation (move/rename), and distinguishes from sibling tools like delete_file or write_text_file by indicating relocation/rename rather than creation, deletion, or modification.

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 implies usage for moving or renaming files/folders but does not explicitly state when to use it over alternatives (e.g., copying via upload/download) or when not to use it. There are no exclusions or alternatives mentioned, so the guidance is only implicit.

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