kali_web_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 of behavioral disclosure. It fails to describe what the tool does operationally (e.g., executes commands, runs scripts, interacts with targets), potential side effects (e.g., network traffic, system changes), security implications, or output format. This leaves the agent with no understanding of the tool's behavior beyond its vague domain.

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 phrase that is too brief and under-specified for a tool with 3 parameters and no annotations. While concise, it lacks necessary detail and structure—it doesn't front-load key information or provide any actionable context. This brevity results in insufficient content rather than efficient communication.

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 (3 parameters, no annotations, no output schema, and many sibling tools), the description is severely incomplete. It doesn't explain the tool's function, behavior, or output, leaving critical gaps for an agent to understand how to use it effectively. The lack of annotations and output schema heightens the need for a more comprehensive description, which is unmet.

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) with descriptions. The description adds no additional meaning about parameters, such as examples of valid tools or typical options. However, with high schema coverage, the baseline score is 3, as the schema handles the parameter documentation adequately.

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 'Web exploitation and analysis tools' restates the tool name 'kali_web_exploitation' without specifying a verb or action. It vaguely indicates the domain (web exploitation/analysis) but doesn't explain what the tool actually does (e.g., execute commands, run scripts, perform scans). This is essentially a tautology that adds little beyond the name.

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 guidance is provided on when to use this tool versus alternatives. With many sibling tools like 'kali_web_scan', 'kali_network_exploitation', and 'run_kali_command', the description offers no differentiation or context for selecting this specific tool over others. It lacks any mention of prerequisites, typical scenarios, or exclusions.

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