connect_runtime

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

Description reveals it uses the controlled browser and waits for a condition, which is a blocking behavior. With no annotations, it partially compensates but lacks details on error handling, authentication, or what happens if browser is not connected.

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?

Single sentence with clear division: action first, then consequence. No unnecessary words; perfectly sized for the tool's simplicity.

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?

Does not mention return value, failure modes, or prerequisites (e.g., open_colab_browser_connection must be called first). Lacks completeness for an agent to understand pre- and post-conditions, despite low complexity.

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 covers waitSeconds with default and bounds (100% coverage). Description adds no extra nuance beyond the schema's description, so baseline of 3 is appropriate.

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?

Description clearly states it connects/reconnects the Colab Python runtime and waits for terminal-backed tools to see kernel.runtime. Action is specific and distinguishable from siblings like run_code_cell or restart_runtime, though could explicitly differentiate from restart_runtime.

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?

No guidance on when to use this tool vs siblings like restart_runtime or open_colab_browser_connection. Does not specify prerequisites or alternatives, leaving the AI to infer usage context.

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