pivot_ssh_local

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

No annotations provided, so description carries full burden. Describes the function adequately but lacks details on side effects (e.g., tunnel persistence, lifecycle, or security considerations like password exposure). Basic but not comprehensive.

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?

Very concise, front-loaded with the purpose in the first line, followed by a clean parameter list. Every sentence adds value.

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 complexity of creating an SSH local port forward (a long-running tunnel) and absence of annotations, the description lacks crucial context: how to stop the tunnel, whether it's blocking, return value details, and prerequisites (e.g., SSH server accessibility). Output schema exists but is not shown in the description.

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 has 0% parameter descriptions, so the description must compensate. It adds meaningful explanations for each parameter in the Args block (e.g., 'ssh_host: SSH server to tunnel through'), providing context beyond the schema's type and title.

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?

Clearly states the action ('Create') and the resource ('SSH local port forward'), with a parenthetical explanation ('access remote service locally'). Distinguishes from sibling tools like pivot_ssh_dynamic and pivot_ssh_remote.

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?

No guidance on when to use this tool versus alternatives (e.g., pivot_ssh_remote, pivot_ssh_dynamic). Does not mention prerequisites or usage context.

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