ssh_tunnel_close

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

With no annotations, the description fully covers behavioral traits: it affects only local state, closing is irreversible, and for the server option it reports count of closed tunnels. No contradictions.

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?

Three well-structured sentences: first states action and scope, second explains options, third warns about finality. Every sentence is necessary and informative—no redundancy.

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 complexity (two optional but mutually exclusive parameters, no output schema), the description completely covers behavior, parameter constraints, and side effects. No gaps remain.

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 already has descriptions for both parameters (100% coverage), but the description adds essential context: the mutual exclusivity rule, that server closes all tunnels, and that the operation reports the number closed—significantly beyond schema.

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 'tears down' as a specific verb for the 'ssh tunnels' resource, clearly distinguishing it from sibling tools like ssh_tunnel_create (creates) and ssh_tunnel_list (lists). It also clarifies scope ('affects only local tunnel state').

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?

Explicitly states that exactly one of tunnelId or server must be supplied, explains what each does, and warns that supplying neither raises an error. The finality ('cannot be undone') provides crucial guidance.

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