colab_fs_list

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

With no annotations, the description carries the full burden. It adds the behavioral warning about runtime replacement and unrecoverable old /content, which is useful context. However, it does not disclose what the tool actually returns (e.g., file names, full paths, pagination) or any potential side effects beyond the implied read-only nature.

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 extremely concise: two short sentences with no fluff. The primary purpose is front-loaded in the first sentence, and the second adds a critical caveat. Every word 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 simple list tool with fully documented parameters and no output schema, the description provides adequate purpose and a relevant runtime lifecycle warning. However, it lacks clarity about the return format and could more explicitly state that it lists files/directories under the given path. The caveat about reacquisition is contextually relevant but somewhat cryptic.

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 the baseline is 3. The description does not add any parameter-specific information beyond what the schema already provides. It only references /content in the caveat, which is already the default value in the schema.

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 'List runtime paths' clearly identifies the action (list) and the resource (runtime paths), and it distinguishes this tool from siblings like colab_fs_read, colab_fs_write, and colab_fs_stat. However, 'runtime paths' is slightly ambiguous and could be more explicit about listing directory contents.

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 provides no explicit guidance on when to use this tool versus alternatives. It mentions a runtime_replaced/missing caveat, but this is more of a behavioral warning than usage guidance. No alternatives are referenced, and no conditions for use are stated.

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