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

All annotations are false hints, so they add no safety profile and the description carries the disclosure burden. It discloses meaningful side effects beyond the schema: copied assignments get a fresh 'pending' status, the subfolder tree is recreated, Drive links are excluded, and owner_model reassigns all copied assignments. Gaps are minor (name-collision behavior, return value), and there is no contradiction with the annotations — the described mutations align with readOnlyHint=false.

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 sentences with no filler, each serving a distinct purpose: core copy behavior, the template-clone use case, and the Drive-link exclusion with its alternative. The primary purpose is front-loaded and every sentence earns its place.

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 five-parameter mutating tool with no output schema and neutral annotations, the description combined with the richly documented schema covers what an agent needs to call it correctly: what gets cloned, how ownership reassignment works, and the Drive-link limitation. What's missing is post-call information — the identity/return value of the copy (needed to chain set_drive_folder) and behavior on name collisions — which prevents a 5.

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 the schema descriptions are already detailed (e.g., owner_model explains reassignment and root-folder ownership; new_name explains the '<source name> (copy)' default). The description adds useful color — cloning a template for a new creator and what 'copies its assignments' means (posts, brief, tags retained, status reset) — but it mostly reinforces rather than fundamentally extends the schema's parameter documentation.

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 a specific verb and resource ('Duplicate a folder') and goes well beyond a tautology by specifying exactly what duplication entails: recreating the subfolder tree and copying assignments with same posts, brief and tags but fresh 'pending' status. This detail distinguishes it from siblings like create_folder (empty folder), move_folders (relocation), and archive_folder (status change).

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?

Provides an explicit when-to-use scenario: cloning a template folder like 'Beginner content' for a new creator via owner_model. Also gives a concrete exclusion with an alternative: 'Drive links are not copied (use set_drive_folder on the copy)'. It does not systematically contrast with all folder-operation siblings (e.g., when to choose create_folder over this), so it stops short of a 5.

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