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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description adds useful context: it specifies that searches are bounded (same workspace, no cycles, depth limit) and that the response is the updated folder row. It is missing auth/rate-limit details but goes beyond the annotations meaningfully.

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 tightly packed sentences with no filler. The core behavior ('Renames, repositions, or moves') is front-loaded, followed by parameter usage and constraints.

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?

There is no output schema, and the description states the return value ('Returns the updated folder row'). All key constraints for a mutation tool (workspace scope, cycles, depth, sibling name uniqueness) are covered, so an agent has what it needs.

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 parent_id: null, uniqueness, cycle constraints, and depth limits. The description largely restates these constraints (plus 'Pass any subset'), so the baseline 3 is appropriate even though it adds no new detail beyond 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 specific verbs and resource: 'Renames, repositions, or moves (reparents) a folder.' The use of 'reparents' distinguishes it from move_video_to_folder at the resource level. However, it does not explicitly name sibling tools like create_folder or delete_folder to differentiate, leaving a slight gap.

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 tells the agent to 'Pass any subset of name / parent_id / position,' which gives usage mechanics. It also states constraints (same workspace, no cycles, max 5 levels, unique sibling names). But it never says when to choose this tool over siblings or when updates are inappropriate, leaving usage implicit.

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