chisel

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

No annotations are provided, so the description carries the burden. It discloses that it encapsulates TCP connections inside HTTP WebSocket streams, which is a key behavioral trait. It also mentions output (connection status and tunnel statistics). However, it doesn't disclose potential side effects like network traffic patterns, persistence, or whether it modifies the system. For a tunneling tool, this is moderate transparency 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?

The description is compact and front-loaded with the core purpose. It covers the key points (protocol, use case, deployment roles, output) in a few sentences. Slightly dense but every sentence earns its place. Could be slightly more structured but overall efficient.

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 5 parameters and no output schema, the description covers the essential context: what it does, when to use it, how to deploy it (server/client roles), and what output to expect. It doesn't explain all parameter combinations in detail, but the schema covers parameter semantics. The description is complete enough for an agent to invoke it correctly in a typical pivoting scenario.

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%, so the schema already documents all 5 parameters. The description adds context for server/client roles and mentions reverse port forwarding, which helps interpret the 'server' and 'port' parameters. However, it doesn't add much beyond the schema's own descriptions, so baseline 3 is appropriate.

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 tool's function: a fast TCP/UDP tunnel over HTTP/HTTPS for pivoting through firewalls and NAT. It names the specific verb (tunnel), the resource (TCP/UDP traffic), and the context (pivoting through firewalls/NAT), which distinguishes it from sibling tools like netcat or proxychains.

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 explicit usage context: run server on attack box, client on pivot host with reverse port forwarding. It also mentions the ideal scenario (tunneling from internal network through compromised host). However, it doesn't explicitly state when not to use it or name alternatives, though the context is clear enough for an agent to select it appropriately.

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