websex_msfvenom

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

With no annotations, the description carries the full burden and does add real value: it discloses that the container executes msfvenom directly with argv tokens and that shell parsing is never used, plus the engagement-namespace scoping. However it omits that this produces payload artifacts on disk, where they land, and any permission or rate-limit context.

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, front-loaded with the verb and the execution model. No filler and every clause carries information an agent needs.

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. Still, for a mutation tool that writes artifacts with 0% parameter coverage and no annotations, the description leaves gaps: stdin semantics and the artifact/output destination are not addressed.

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 coverage is 0%, so the description should compensate. It partially does: 'arguments' are clarified as argv tokens, 'engagement_id' maps to the selected namespace, and 'working_directory' is implied by the relative-path guidance. The 'stdin' parameter is entirely unexplained in both schema and description.

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 msfvenom'), naming the exact binary and toolkit. It is distinguishable from most siblings by naming msfvenom, though it never explicitly contrasts itself with the closer alternatives like websex_payload_encode or websex_metasploit.

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 hints (relative paths for engagement artifacts) but no guidance on when to use this tool versus the many payload/exploit siblings (payload_encode, exploit_search, metasploit). The agent is left to infer the selection criteria.

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