pivot_chisel_server

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

With no annotations provided, the description carries the full burden of explaining side effects or runtime behavior. 'Start chisel server' implies launching a process but does not disclose whether it runs in the background, how to stop it, or what dependencies or privileges are required.

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, compact sentence with no filler words. It is appropriately sized for the tool's simplicity, though it is so terse that it sacrifices useful context for brevity.

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 tool with no annotations, no output schema, and two untyped parameters, the description is severely inadequate. It does not explain the role of a chisel server in pivoting, what 'reverse' means, or how this tool relates to the broader pivot workflow, leaving the agent without essential context.

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 input schema lists 'port' and 'reverse' with defaults, but schema description coverage is 0% and the tool description gives no additional meaning. The term 'reverse' is ambiguous (e.g., reverse tunneling mode) and the agent receives no explanation of how these parameters affect the server.

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 ('Start') and the resource ('chisel server'), which is a specific verb+resource pair. However, it does not itself differentiate the server from sibling tools like pivot_chisel_client, relying on the tool name for that distinction.

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?

There is no guidance on when to use this tool versus alternatives such as pivot_chisel_client or other pivoting tools. The description gives no context about prerequisites, complementary tools, or scenarios where the server is appropriate.

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