Stop the Colab GPU session immediately and release hardware to prevent unnecessary Compute Unit charges. Optionally provide a reason for ending the session.
Stop the Colab GPU session immediately and release hardware to avoid unnecessary Compute Unit charges.
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | Optional human-readable reason for stopping the session. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description still discloses the key effects: termination is immediate, hardware is released, and billing stops accruing. It omits whether in-flight work is lost, whether the call is idempotent if the session is already stopped, and that gate_wake is required to resume.
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?
One front-loaded sentence with the action first and the motivation second; every clause earns its place with no 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?
For a zero-required-parameter action tool with no output schema, the description covers what happens and why. The remaining gap is recoverability — that the session must be woken again via a sibling — which an agent could infer but is not stated.
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% for the single optional 'reason' parameter, so the schema already documents it fully. The description adds nothing about the parameter, making the baseline of 3 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?
Names a specific verb and resource: stop the Colab GPU session and release its hardware. The intent is unmistakable against gate_status and gate_wake, though neither 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?
The clause 'to avoid unnecessary Compute Unit charges' implies the condition for calling it (GPU idle or no longer needed), but there is no explicit when-not-to-use guidance and no instruction to use gate_wake for restarting.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.