Stop all tunnels

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

The annotations already include destructiveHint=true, so the baseline bar is lower. The description adds meaningful context by specifying that the action affects every active tunnel and revokes public URLs, which goes beyond a generic destructive label.

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?

The description is two sentences with no wasted words. The primary scoping statement comes first, followed by a useful pointer to the sibling tool.

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?

Given no parameters, no output schema, and a destructiveHint annotation, the description fully covers the essential context: what the tool does, its scope, and the alternative for a narrower operation. Nothing critical is missing for correct invocation.

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?

With zero parameters, the schema is fully covered and the description cannot add parameter-level detail. The baseline of 4 is appropriate because there is nothing missing for the agent to understand about inputs.

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 states a precise verb and resource ('Stop every active tunnel') and clarifies the consequence ('revoking all public URLs'). It also distinguishes itself from the sibling tool stop_tunnel by explicitly naming the single-tunnel alternative.

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?

Provides explicit usage guidance by saying when to use this tool (to stop every tunnel) and when to use the alternative ('To stop a single tunnel, use stop_tunnel instead'). This leaves no ambiguity about tool selection.

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