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

It discloses slug reassignment, publishing and address side effects in the Marketing folder, permission changes, the immutable Marketing folder, and the recovery path. Since annotations only provide idempotent and non-destructive hints, the description carries the behavioral burden and does so thoroughly. No contradiction with annotations.

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?

There is no filler, but the middle is a run-on, parenthetical-heavy paragraph that is hard to scan, and the critical self/descendant constraint is buried near the end. The purpose is front-loaded, but the side-effect list would be much easier for an agent to parse as structured bullets.

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 write tool with no output schema, the description covers the operation, return value, result naming, recovery instructions, constraints, and workspace-specific side effects. Combined with the schema's already thorough workspace_id description, an agent has what it needs to call the tool correctly.

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 the baseline is 3; the description still adds value by telling the caller to source folder_id and parent_id from list_folders and by tying parent_id omission to drive-root movement. It does not add new meaning for space or workspace_id, but those are already well described in the schema.

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 description opens with the specific operation 'Re-parent a folder' and elaborates through parent_id and root-moving, making it clearly a folder-move tool rather than rename_folder or set_folder_slug. It is not a 5 because it never names a sibling such as move_site_to_folder, so the agent must infer the boundary from the word 'folder'.

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 gives clear context: how to supply IDs from list_folders, omit parent_id to move to the root, and the prohibited self/descendant move. It also distinguishes shared-drive behavior from website-workspace behavior. It does not explicitly list alternatives, but the context is strong enough to guide selection.

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