websex_dotdotpwn

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

With no annotations, the description carries the full burden. It usefully discloses that the container executes dotdotpwn directly with argv tokens and that shell parsing is never used, and that paths are resolved relative to the engagement namespace. It does not describe the actual operation, expected runtime, or any auth/safety profile beyond the no-shell behavior.

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 tight sentences with the action front-loaded and no filler. The no-shell and relative-path notes earn their place; nothing is redundant.

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 described, but with zero annotations and a 4-param schema at 0% coverage, the description leaves the tool's actual purpose (traversal fuzzing methodology) implicit and doesn't fully compensate for the parameter documentation gap.

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 4 parameters. The description adds meaning for `arguments` ('supplied argv tokens'), `engagement_id` ('selected engagement namespace'), and `working_directory` ('relative paths for engagement artifacts'), but leaves `stdin` unexplained and gives no format or example for argv tokens.

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 and resource: 'Run dotdotpwn'. However, it does not explain what dotdotpwn is (a directory/file traversal fuzzer) nor distinguish it from sibling wrappers like websex_traversal_probe or websex_execute, so an agent must already know the tool's function.

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 websex_traversal_probe or a generic executor. It mentions running from the engagement namespace and using relative paths, but that is operational context, not a when/when-not/alternative rule.

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