colab_notebook_run_cell

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

No annotations are provided, so the description carries the full burden, and it does disclose real behavior: state persists between cells, output is written into the notebook, status is reported as ok/ERROR, and displayed plots land in .colab-mcp/images/. It stops short of covering session/auth requirements, timeout behavior, or what happens on error.

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?

Three short, front-loaded sentences with no filler: the action, the state-persistence caveat, the status report, and the artifact location each earn their 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?

An output schema exists so return values need not be described, and the description usefully adds status and artifact-path detail anyway. However, with zero schema description coverage and no annotations, the undocumented session and timeout parameters leave the definition short of what an agent needs to invoke it confidently.

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 0%, so the description must explain the four parameters, yet it only gestures at 'cell' (a code cell) and mentions no meaning for path, session, or timeout (which defaults to 300s). Three of four parameters remain opaque to the agent.

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 ('Run ONE code cell on the runtime') plus the side effect of persisting output into the notebook. The emphasis on ONE implicitly distinguishes it from the sibling colab_notebook_run_all, though no sibling is named explicitly.

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 rather than stated: running a single cell with persistent state suggests pairing with colab_notebook_run_all or colab_exec, but neither alternative is named nor is a when-not condition given. An agent must infer the routing from the tool names alone.

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