run_network_exploit

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

No annotations are provided, so the description must fully disclose behavioral traits. It offers only a bare list of exploit_type values ('ssh_brute,' 'ftp_brute,' etc.) with no details on side effects, required permissions, impact on target systems (e.g., potential intrusiveness, reversibility), or any error handling. The absence of any behavioral or safety information makes it poorly transparent for an 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?

The description is only two lines, but one line is a code-like list that should be prose or integrated. While short, it is under-specified to the point of being unhelpful; conciseness at the expense of completeness is not virtuous here. There is no front-loading of key decisions like prerequisites or output.

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?

Given the tool's complexity (3 parameters including a nested object, no output schema, many siblings), the description is drastically incomplete. It fails to explain the required 'target_ip' format, what 'options' contains, what happens on success/failure, or how results are returned. The agent cannot confidently invoke this tool correctly with the provided information.

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%, and the description only mentions 'exploit_type' examples in a code block, not in prose. The 'target_ip' parameter is not explained at all. The 'options' object is present but its semantics (what fields it accepts, default behavior) are entirely undocumented. The description adds marginal value, and with no param docs in the schema, the agent lacks critical context.

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?

The title is null, and the description says 'Run network exploitation tools.' This is extremely vague: it doesn't specify what actions it performs (e.g., brute-forcing, checking credentials), or what resource it operates on beyond a vague 'network.' It lists example exploit types, but the tool name itself ('run_network_exploit') could also describe the sibling 'run_exploit,' causing confusion. It lacks a specific verb-resource combination.

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. Given 30+ siblings like 'scan_local_network,' 'brute_force_login,' 'exploit_smb,' and 'run_exploit,' the description provides zero context about which scenarios favor this tool. It does not mention prerequisites, when not to use it, or what distinguishes it from similar tools.

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