websex_socat

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

With no annotations, the description carries the full burden, and it does disclose two meaningful traits: shell parsing is never used (args passed as raw tokens) and execution is scoped to the engagement namespace. It omits side-effect warnings (socat can open listening sockets), blocking/timeout behavior, and permission requirements, which are significant for an arbitrary CLI passthrough.

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?

Three sentences, front-loaded with the core action, no filler. Slightly dense with operational asides but every sentence contributes context.

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?

An output schema exists so return values needn't be described, and the execution mechanics are covered. However, for a tool that wraps an arbitrary network binary with no annotations, the description is thin on safety, side effects, and timeouts that an agent would need to invoke it responsibly.

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 0%, so the description must compensate. It loosely maps to three of four params ('argv tokens' -> arguments, 'relative paths for engagement artifacts' -> working_directory, 'engagement namespace' -> engagement_id) but says nothing about stdin and never ties terms to the schema field names.

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?

States a specific verb+resource ('Run socat') and clarifies it is executed directly with argv tokens rather than through a shell. This differentiates it conceptually from shell-based siblings like websex_bash, though it never names an alternative. Purpose is clear but not explicitly positioned against siblings.

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 choose socat over the many related siblings (bash, python, curl, nmap, etc.), nor any when-not or prerequisite statement. The only operational hint is 'use relative paths for engagement artifacts,' which describes how rather than when to use the tool.

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