websex_responder

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

With no annotations, the description carries the full burden and does disclose real behavioral traits: the container executes `responder` directly with argv tokens and never uses shell parsing (an important injection/quoting note), plus the working-directory/namespace behavior. It omits significant context for a network poisoning/credential-capture tool, such as privilege requirements, network binding, and whether it blocks or times out.

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 compact sentences with no filler, and the core action ('Run responder...') is front-loaded. The execution-safety detail is placed second, which is reasonable, though the namespace/path sentence could be merged without loss.

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 need not be explained. But with no annotations and zero parameter descriptions, the description is the only source of behavioral and parameter information, and it leaves gaps around what responder actually does, its privilege/network requirements, and the stdin parameter.

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 maps meaning onto `arguments` (argv tokens), `engagement_id` (engagement namespace), and `working_directory` (relative artifact paths), but says nothing about the `stdin` parameter, leaving one of four parameters entirely undocumented.

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 (run) and resource (responder from the WebSex enumeration toolkit), which is clear enough to distinguish it from unrelated siblings. However, it never distinguishes itself from the generic execution siblings (websex_execute, websex_bash, websex_python), so an agent cannot tell from the description why it should pick this wrapper over a generic shell runner.

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?

Provides some operational context: it runs from the selected engagement namespace and relative paths should be used for engagement artifacts. There is no explicit when-to-use versus the generic execute/bash siblings and no when-not-to-use guidance, so usage is only implied.

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