Move or rename a document or subfolder

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

Annotations declare the safety profile (readOnly=false, destructive=false, openWorld=false), and the description adds substantial behavior beyond that: incoming [[wikilinks]] and relative Markdown links in any document are rewritten, the result enumerates updated documents, missing parent folders are created, and nothing is overwritten. These are exactly the side effects an agent must anticipate before mutating paths.

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?

Purpose, side effects, safety guarantee, and alternative are each delivered in one front-loaded clause with no filler or repetition of the title.

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?

No output schema exists, but the description states what the result contains (the documents that were updated), and annotations plus the description together cover side effects and safety. Nothing needed to invoke this correctly is missing.

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 100%, and the schema already explains both `from` and `to` semantics including the extension and auto-created folders, so the baseline is 3. The description only adds the constraint that the destination is "inside the documents folder," which is mild extra value.

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+resource with scope: "Rename or move a document, or a subfolder with everything in it, to a new path inside the documents folder." It distinguishes itself from ragdown_edit and ragdown_delete by naming them, so an agent can route without opening the schema.

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?

Gives an explicit replace-this condition: "Use this rather than ragdown_edit plus a delete, which would break the links." It also states the failure condition up front ("Never overwrites: if something is already at `to`, nothing moves"), so when-to-use and when-not are both covered.

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