colab_fs_read

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

With no annotations, the description must disclose behavior, but it only mentions offset and incarnation handling. It does not explain return format (e.g., base64, next_offset), error behavior, or session concurrency rules, leaving significant behavioral 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 extremely concise at two sentences, with the purpose front-loaded and the usage guidance following. Every word contributes meaning, with no redundancy or filler.

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 lack of annotations and output schema, the description leaves out important context like the base64 return encoding, the presence of next_offset in responses, and detailed session behavior. It is minimally complete with the schema filling in parameter details, but not fully self-sufficient.

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 100%, so the schema already fully describes all parameters (path, limit, offset, session). The description adds no extra parameter semantics beyond implying a chunked read, which is adequate given the high schema coverage.

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 states 'Read a chunk,' which clearly indicates a read operation on a file resource, supported by the 'path' parameter. It differentiates from sibling tools like colab_fs_write and colab_fs_list by specifying a chunked read, though it does not explicitly name the resource as 'file'.

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 instruction 'Keep next_offset; after incarnation change restart from restored source' provides clear guidance on how to use the tool for sequential reads and how to handle session changes. It does not explicitly compare to alternatives, but the context is sufficient for a read operation.

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