kali_network_exploitation

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 vaguely mentions 'exploitation and post-exploitation' but doesn't disclose behavioral traits such as whether it's read-only or destructive, permission requirements, rate limits, or output format. This is inadequate for a tool that likely involves security testing operations.

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 a single, efficient phrase: 'Network exploitation and post-exploitation tools'. It's front-loaded and wastes no words, though it could be more informative. However, it's appropriately sized for a tool name that hints at its function.

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 complexity of network exploitation tools, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool does operationally, what to expect as output, or safety considerations, making it inadequate for an agent to use effectively in a security context.

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 parameters (tool, target, options). The description adds no additional meaning beyond what's in the schema, such as examples of tool usage or context for options. Baseline 3 is appropriate as the schema does the heavy lifting.

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 description 'Network exploitation and post-exploitation tools' states a general purpose but lacks specificity. It mentions a category of tools rather than what this particular tool does (e.g., execute or manage these tools). It distinguishes from siblings like 'kali_network_scan' by focusing on exploitation rather than scanning, but doesn't specify the verb or resource clearly.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for network exploitation, but it doesn't specify prerequisites, contexts, or exclusions compared to siblings like 'kali_web_exploitation' or 'kali_vulnerability_scan', leaving the agent to infer based on tool names alone.

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