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

With destructiveHint=true and idempotentHint=false already declared, the description still adds real value: inherited folder/content access may be lost, moving to root disables limited access, a return to the original state requires current permissions and is not restored automatically, and lost access can reassign scheduled emails to the contract owner. That is substantive consequence disclosure beyond the 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?

Dense and front-loaded with the operation and its validation rules before the side effects. A few clauses are telegraphic to the point of ambiguity, notably 'return needs current permissions and does not restore it', which costs some clarity.

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 two-parameter destructive move with no output schema, it covers rejection conditions, access-loss consequences, and the root special case. What is missing is only the direct comparison to sibling move/rename tools and any explicit statement about the response.

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% and parentFolderId already documents null=root, but the description adds meaning the schema lacks: the destination must be a visible/authorized parent, and moving to root specifically disables limited access. That constrains how parentFolderId may legitimately be set.

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 a specific verb (Move) and implies the resource via 'visible parent/root' and 'folder/content access', matching the title and id. It is clear what happens, though it never explicitly names the folder resource or distinguishes itself from the sibling clm_move_contract.

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 preconditions rather than selection guidance: destinations must be visible, and cycles or unauthorized destinations are rejected. There is no explicit when-to-use versus clm_move_contract or clm_rename_folder, so routing guidance is implied rather than stated.

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