pivot_stop_all_tunnels

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It only states the literal action and does not mention potential side effects, such as disrupting all active tunnels, whether it is reversible, or any required permissions. This lack of depth is notable for a bulk 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?

The description is a single short sentence with no superfluous words. It is appropriately sized for a zero-parameter tool and is front-loaded with the key action.

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 the tool's simplicity, the description is minimally adequate, stating the function clearly. However, it lacks any broader context such as impact on active sessions or how this differs from stopping individual tunnels, which would make it more complete for an agent deciding to invoke it.

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 has zero parameters, and the schema is complete with an empty properties object. The baseline for zero parameters is 4, and the description adds no unnecessary parameter details, which 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?

The description clearly states the action ('stop') and the resource ('all tunnels'), and the word 'all' scope distinguishes it from the sibling tool 'pivot_stop_tunnel' which targets a single tunnel. This is a specific and unambiguous description.

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?

There is no guidance on when to use this tool versus alternatives. The sibling tool 'pivot_stop_tunnel' exists, but the description does not mention it or any exclusions, leaving usage decisions to the agent without additional context.

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