pivot_ssh_dynamic

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It gives zero information about side effects, long-running behavior, connection lifecycle, stopping the tunnel, or any prerequisites. The description is completely opaque regarding behavior.

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 noun phrase with no wasted words, but it is severely under-specified. This is not effective conciseness; it omits essential information. Similar to the 'Process' example, the brevity harms usability.

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 network pivot tool with two parameters, no annotations, no output schema, and no parameter descriptions, the description provides almost no context. It does not explain operation semantics, return behavior, or how the tunnel is managed. While the tool is relatively simple, the description is still incomplete for safe and 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?

The schema has two parameters (local_port, ssh_target) with no descriptions and 0% schema coverage. The description 'SSH dynamic SOCKS' only weakly implies that local_port is the local SOCKS port and ssh_target is the SSH server, but it does not explicitly explain their roles or expected formats. It fails to compensate for the lack of schema documentation.

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 phrase 'SSH dynamic SOCKS' identifies the tool as related to SSH dynamic SOCKS proxying, but lacks an explicit verb or action (e.g., 'Create a dynamic SOCKS tunnel'). It is somewhat clear but does not fully state what the tool does or distinguish it from sibling tools like pivot_ssh_local or 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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of typical scenarios, prerequisites, or exclusions. An agent would have to infer usage purely from the tool name and sibling context.

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