Stop SSH Port Forward

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

Annotations already declare readOnlyHint=false and destructiveHint=false, signaling a mutating but non-destructive operation. The description adds the context that it stops a tunnel created by the start tool, but it does not disclose failure modes, side effects on other tunnels, or whether the operation is reversible. This adds some value beyond annotations but lacks rich behavioral detail.

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, succinct sentence that immediately states the tool's purpose with no filler. Every word earns its place, and it is well-structured for quick parsing by an AI agent.

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 stop operation with one parameter, the description and schema together cover the essentials. The reference to the start tool provides context, and there is no output schema requiring explanation. It could mention return behavior or error handling, but these are not critical given the tool's straightforward nature.

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 description coverage is 100% (the 'id' parameter is fully described). The description adds no additional parameter semantics beyond what the schema provides. Per the rubric, high schema coverage yields a baseline of 3, and there is no compensating information in the description.

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 a tunnel' and references the specific start tool, distinguishing it from sibling tools like remote_ssh_list_port_forwards or remote_ssh_start_port_forward. The verb 'stop' plus the resource 'tunnel' make the purpose unambiguous.

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 description implies when to use it: to stop a tunnel previously created by remote_ssh_start_port_forward. It provides clear context and differentiates from siblings by referencing the start tool, though it does not explicitly mention alternatives or when not to use it. For a simple inverse operation, this is adequate.

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