colab_stop

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

With no annotations provided, the description fully shoulders the burden. It discloses idempotency ('idempotently') and the destructive consequence ('permanently loses RAM and /content'), which is critical for a stop operation.

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, front-loaded with the core action, followed by a necessary warning. No fluff.

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 single-parameter tool with full schema coverage, the description covers the essential action, idempotency, and the key destructive side effect. No output schema exists, so return value documentation is not required. It is complete for the tool's 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?

The input schema already provides a complete description for the 'session' parameter (100% coverage), and the tool description adds no additional parameter detail. Baseline of 3 applies.

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 uses a specific verb-resource pair ('Release compute') and clearly distinguishes this from sibling tools like colab_pause_notebook and colab_start by emphasizing permanent shutdown and idempotency. Could be slightly more explicit that it stops a session, but 'release compute' is clear in context.

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 phrase 'Export first; stopping permanently loses RAM and /content' gives an explicit prerequisite and warning, conveying that this should only be used when the user is ready to permanently discard session state. It doesn't name alternatives like pause, but the context is clear.

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