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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds a genuine behavioral rule beyond annotations: a folder cannot be moved into itself or its own subfolders, which tells the agent about a validation failure mode it must avoid.

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, zero filler, with the capability stated first and the operational and constraint details following in priority order. Nothing could be removed without losing information.

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 and the input schema is fully documented, so the description only needs to cover intent and constraints, which it does. The main remaining gap is that it says nothing about permissions or what happens to a folder's contents when it is moved.

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 every parameter is already documented in the schema, including parentId accepting null or 'root' and name being optional. The description largely restates the null-to-top-level behavior rather than adding new semantics, so the baseline 3 applies.

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 opening sentence names the specific resource (folder) and the two operations it supports (rename, reparent), which lets an agent tell it apart from create_folder/delete_folder. It never explicitly contrasts itself with move_file, though the folder-vs-file distinction is implied only by the noun.

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?

It states the key operational condition (pass parentId: null to return to top level, omit to leave unchanged) and one hard constraint (no moving into self/subfolders). However, it gives no guidance on when to prefer this tool over a sibling such as move_file, and no prerequisites or permission context are mentioned.

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