Move or rename Nextcloud file

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

Annotations already declare destructiveHint=true, non-idempotent, and closed-world, so the safety profile is known; the description adds a genuine constraint that both paths stay inside the same account and root. However, it omits the critical behavioral fact for a destructive tool: what happens when the destination already exists, and whether an existing file is silently clobbered, rejected, or gated by the overwrite flag.

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?

Two short sentences, and the core action leads. The second sentence earns its place as a scoping constraint, though it is slightly padded ("to another host or recipient") for a closed-world tool.

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?

An output schema exists, so return values need not be described, and annotations cover safety. The remaining gap is meaningful for a destructive, non-idempotent mutation: the overwrite default of false and its consequences are left entirely undocumented.

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 carries the full burden, yet it never mentions the overwrite parameter at all, nor the path format (absolute vs. root-relative) or whether destination may be a directory. Only the vague notion of 'source' and 'both paths' is conveyed.

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?

States a specific verb pair (move/rename) and the resource (an item) plus its scope (within the user's connected private Nextcloud workspace root). This is enough to distinguish it from siblings like delete_file, create_folder, or write_text_file, though it does not name an alternative explicitly.

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?

Implicitly tells the agent when to use it (relocating or renaming an existing item) and adds a useful exclusion: no cross-host or cross-recipient transfers. It gives no guidance on when to prefer this over upload/download-style tools, nor on overwrite vs. fail-if-exists behavior.

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