copy_drive_folder

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

With no annotations, the description carries full burden. It discloses recursive copy and sequential processing to avoid rate-limit errors, but fails to mention permissions handling, overwrite behavior, or file size limits. This is adequate but has notable gaps.

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?

The description is two sentences: the first succinctly defines the action, the second adds key details (tree walk, sequential). No redundant or unnecessary information. Perfectly front-loaded and concise.

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?

Given the tool's complexity (4 params, no annotations, output schema exists), the description covers recursive nature and sequential processing but omits error handling, permission requirements, and what happens on naming conflicts. Sufficient but not fully comprehensive.

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 75%, and the existing schema descriptions are clear. The tool description does not add extra meaning beyond the schema for parameters; e.g., 'user_google_email' lacks description in both. Baseline of 3 is appropriate.

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 clearly states the tool recursively copies a Drive folder and all its contents to a new location. It explicitly mentions 'sequential' behavior to avoid rate-limit errors, distinguishing it from sibling tools like copy_drive_file (single file) and create_drive_folder (empty 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?

The description implies the tool is for copying entire folder trees but does not explicitly state when to use it over alternatives like copy_drive_file for single files or create_drive_folder for empty folders. No when-not-to-use guidance is provided, which is a gap given the large list of sibling tools.

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