colab_download_dir

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

With no annotations, the description carries the full burden and does meaningful work: it discloses zip-slip protection (refuses archives escaping the target) and a size cap with the exact env var and default (COLAB_MCP_MAX_DOWNLOAD_MB, 1024). It omits session/auth requirements and what happens on partial transfer.

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?

Two sentences, front-loaded with the action and target, followed by the failure constraints. No filler; every clause adds usable information.

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?

An output schema exists so return values need no explanation, and the safety constraints are covered. The gaps are the undocumented session parameter and the absence of annotation-level detail on permissions, which a 3-param mutation-of-local-state tool could reasonably specify.

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 0%, so the description must compensate. It clarifies that local_dir is resolved inside the working directory and implies remote_dir is the source folder, but the session parameter is left completely unexplained in both schema and description.

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 ('Download a whole VM folder ... via one zip'), and the word 'whole'/'folder' implicitly separates it from the file-oriented colab_download and the inverse colab_upload_dir. It stops short of naming those siblings explicitly, so an agent must infer the boundary.

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?

Usage is implied by 'whole VM folder' versus the single-file download sibling, and the refusal conditions hint at when the call will fail. There is no explicit statement of when to prefer this tool over colab_download or colab_ls, nor of prerequisites.

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