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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is carried structurally. The description only adds the root-move semantics and an endpoint pointer, and it never explains why the operation is flagged destructive (e.g., effect on contained files/subfolders) – a meaningful gap for a flagged-destructive mutation.

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 covers both behaviors efficiently. The trailing 'Mirrors PATCH /api/v1/folders/{folder}' is mildly redundant but short and provides an API mapping for agents that reason over REST endpoints.

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 three-parameter mutation with full schema coverage and complete annotations, the description covers the essential operations and the null-parent case. It is nearly complete, with the only real omission being the downstream effect of moving a folder (children/contents), which matters given destructiveHint=true.

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%, so all three parameters (name, folder, parent_id) are already documented with types and constraints. The description's note that parent_id null moves to root duplicates the schema text 'New parent folder UUID, or null for the root', adding no new semantics.

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 two specific operations on a specific resource: rename and move a folder. The 'move it under another parent' phrasing implicitly separates it from move_files_to_folder (which relocates files) and update_media/update_stream siblings, though no sibling is named 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?

Use is implied by the rename/move verbs, and the parent_id=null-to-root rule is stated, but there is no explicit when-to-use/when-not guidance and no mention of prerequisites (e.g., needing the target parent to exist or permissions).

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