metasploit_exec

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

No annotations are provided, so the description carries the full burden. It discloses that execution is non-interactive, runs a single module, and exits cleanly, which is useful behavioral context. However, it says nothing about required privileges, side effects on the target, timeout behavior, or whether the output is captured, leaving materially important traits undisclosed for a remote exploitation tool.

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 core action and execution context, followed by a scoping constraint. Efficient and free of filler, though the final authorization sentence could arguably be considered boilerplate rather than tool-selection-relevant.

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?

For a 4-parameter remote exploitation tool with no annotations and no output schema, the description covers purpose, method, and authorization scope. It omits operational expectations an agent would need to call it safely and correctly, such as session handling, expected output, and error behavior. Adequate but with clear gaps.

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 100%, so the schema already documents all four parameters including examples and the run_command enum. The description adds no parameter-level detail beyond what the schema provides. Per the rubric baseline, this is a 3.

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 ('Execute') and resource ('Metasploit Framework module') plus the execution context (non-interactively on remote Kali via msfconsole). It is distinguishable from siblings like nmap_scan or sqlmap_scan, but it does not explicitly contrast with shell_exec, which could also run arbitrary commands. Clear purpose, but sibling differentiation is implicit rather than stated.

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 the authorization constraint ('Only for authorized penetration testing engagements') and specifies single-module non-interactive execution, implying when to use it. However, it gives no explicit when-to-use vs alternatives guidance, such as when to pick this over shell_exec or sqlmap_scan. Usage context is implied but not fully delineated.

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