Move or rename

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description still adds real behavioral detail beyond that: overwrite defaults to false, and the server refuses to move the files root or a folder into itself, which tells the agent about failure modes it would otherwise have to discover.

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?

Three short sentences with zero waste; the core operation is front-loaded and the constraints follow compactly. Nothing needs trimming.

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 no output schema, the description need not describe return values, and it covers the operation, the default, and the guarded failure cases. It is nearly complete for a simple mutation tool; only the result/state after a move is left unspecified.

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 all three parameters are fully documented in the schema. The description's note that overwrite defaults to false duplicates the schema, and it adds no syntax or format details for from/to beyond what the schema already states. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (move/rename) and resource (file or folder) and even names the underlying protocol (WebDAV MOVE). It does not distinguish itself from sibling tools such as delete or write_file, but the operation is unambiguous on its own.

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 'or rename' phrasing implicitly tells the agent that renaming is done through this same call rather than a separate tool, and the caveats hint at invalid uses. However, no alternatives (e.g., delete, write_file) are named and there is no explicit when-to-use guidance.

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