drive_upload_folder

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

With no annotations, the description carries the full load; it does add real behavioral detail — recursion, hidden files skipped, and that a new Drive folder is created as a side effect. It omits partial-failure behavior, permission/auth requirements, and what the tool returns after a multi-file upload.

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?

A single sentence that front-loads the action and then qualifies it with the two behavioral facts that matter (recursive, hidden files skipped). No wasted words.

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 operation with fully documented schema, the description covers the scope and the recursion/skip semantics well. The remaining gap is the absence of any indication of the result of a bulk upload (created folder reference, per-file failures), which matters for a tool that may upload dozens of files.

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%, so all five parameters (name, path, timeout, local_dir, max_files) are already documented, including defaults. The description adds no parameter-level detail beyond confirming that the local folder's contents are what get uploaded; baseline 3 applies.

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 (upload a folder from this computer) plus the concrete effect: creates a Drive folder and uploads files and sub-folders recursively. This implicitly separates it from drive_upload_files and drive_upload, but it never names those siblings, so the differentiation is inferred rather than stated.

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 phrase 'from this computer' and the folder-level scope imply this is for whole-directory transfers rather than single files, but the description gives no explicit when-to-use/when-not guidance and never points to the sibling tools for files or single uploads.

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