websex_ropgadget

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

With no annotations, the description carries the full burden. It does disclose a genuinely useful execution trait: argv tokens are passed directly and shell parsing is never used, which tells the agent quoting/escaping is irrelevant. However it says nothing about output volume, timeouts, failure modes, or permissions, so the disclosure is partial.

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 no filler, and the core action is front-loaded ahead of the execution and path details. Nothing is redundant, though the sentences are more operational notes than a structured definition.

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 annotation coverage, 0% parameter documentation, and a required engagement_id, the definition is only minimally sufficient for an agent to invoke this correctly beyond guessing at the argument format.

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, so the description must compensate and largely does not. 'argv tokens' loosely maps to arguments and 'relative paths' gestures at working_directory, but engagement_id and stdin are never explained, and no format, default, or constraint is added for any of them.

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 (ROPgadget from the WebSex binary toolkit), so an agent knows it is a wrapper that executes an external binary. It does not distinguish itself from the closely related siblings websex_ropper and websex_one_gadget, which is its only real gap.

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 gives operational context ('runs from the selected engagement namespace; use relative paths for engagement artifacts') which implies when it fits, but it never states when to prefer this over ropper or one_gadget, nor any prerequisites beyond the engagement scope. Usage is implied rather than prescribed.

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