websex_xsser

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 add real value by disclosing the execution model: xsser is invoked directly with argv tokens and 'shell parsing is never used', plus the engagement-namespace scoping. It stops short of stating whether the tool is safe/read-only versus actively attacking targets, or what permissions/context it needs, which matters for an offensive scanner.

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 action, and each sentence carries distinct information (what runs, how it executes, where artifacts live). No filler or repetition.

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 model is well covered. But for a 4-parameter tool with 0% schema coverage, the lack of parameter explanation and sibling differentiation leaves the definition only minimally complete.

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% across four parameters, so the description must compensate and largely does not. It only hints at 'argv tokens' (arguments) and 'relative paths' (working_directory), leaving engagement_id and stdin entirely unexplained.

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 ('xsser from the WebSex web toolkit'), so the core action is unambiguous. However, it does nothing to distinguish this from the many sibling XSS tools (websex_dalfox, websex_xss_probe, websex_jaeles, websex_zap), so an agent gets no help choosing among them.

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 only guidance is operational ('Runs from the selected engagement namespace; use relative paths'), which is about how to invoke rather than when. There is no statement of when to pick this over the sibling XSS scanners/probes, and no prerequisites or exclusions.

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