colab_process_export

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

In the absence of annotations, the description does disclose some behavioral traits: atomicity and failure behavior (holding runtime/stage and retry capability). However, it omits side effects, permissions, or what happens on success, so it only partially carries the transparency burden.

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 very short (two sentences), which is concise but at the expense of clarity. It is front-loaded with 'Export', but the first sentence is vague and the overall structure lacks essential context.

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 (12 parameters, no output schema, no annotations), the description is incomplete. It does not explain what is exported, how remote_path/local_path relate, or what the result/return is. The sparse description is insufficient for a tool of this scope.

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 12 parameters are documented in the input schema. The description adds nothing about parameters, but this is acceptable because the schema already provides thorough meaning.

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 says 'Export atomically' but never states what resource is being exported or what operation it performs beyond the name. It does not distinguish from sibling tools like colab_process_export_cleanup or colab_transfer_download, making the purpose vague and close to a tautology.

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?

There is no guidance on when to use this tool versus alternatives. The only usage-related note is about failure recovery ('retry same call from recoverable_export'), but it does not explain use cases, prerequisites, or when not to use it.

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