pivot_chisel_client

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Start chisel client' and fails to disclose that this establishes a network tunnel, may create listeners or connections, or has side effects like process persistence.

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 extremely short, but this is under-specification rather than effective conciseness. It omits critical context that would be necessary for correct invocation.

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 tunneling tool with three parameters and no output schema or annotations, the one-line description is grossly incomplete. It fails to explain the tool's role, parameters, or expected behavior in the context of the pivot toolchain.

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?

All three parameters (server, remote, local) are undocumented in both the schema and the description. The description adds no meaning to these fields, leaving the agent without any understanding of what values to provide.

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 'Start chisel client' directly restates the tool name without elaborating on what a chisel client does or how it fits into the pivot toolset. It lacks the specificity needed to distinguish it from related tools like pivot_chisel_server or pivot_ssh_local.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., a running chisel server) or scenarios where this is preferred over SSH pivoting or socat forwarding.

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