colab_connection_status

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

With no annotations, the description carries the full burden, and it does disclose the key trait: this is a non-mutating query that will not spawn or alter a browser session. It does not say what happens when no session exists (error vs. disconnected result) or whether the reported state is live or cached, which are the remaining behavioral unknowns for a status probe.

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 short sentences, zero waste. The positive capability is front-loaded and the negative scoping clause follows immediately where it is most useful.

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-value shape is already covered and the description needn't restate it; for a zero-param read tool this is nearly enough. Only the no-session / failure behavior is left unstated, a minor gap given the tool's simplicity.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly makes no attempt to describe inputs, and the empty schema is self-explanatory.

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 ("Reports") and a precise resource (connection state of a Colab browser session plus the notebook it was opened for). The closing clause "Does not open a browser" explicitly separates it from the sibling open_colab_browser_connection, so an agent can route without opening either schema.

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 "Does not open a browser" clause is a genuine when-not boundary that tells the agent this is the inspection path, not the connection path. It stops short of naming open_colab_browser_connection as the alternative to call when a session needs to be created, so it is clear context rather than full when/when-not/alternatives routing.

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