kali_exec

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

The description discloses key behavioral traits: no restrictions and full root access. However, it does not mention potential destructiveness, output behavior, or error handling. With no annotations to provide safety hints, this partial disclosure is not enough for a privileged command execution 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 extremely concise, using two short sentences with no wasted words. It front-loads the core action and privilege level immediately.

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 4 parameters, lack of output schema, and dangerous capability, the description is insufficient. It does not explain how output is returned, how parameters affect execution, or which context warrants use. It is a bare minimum that leaves critical 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 0%, and the description does not compensate. It only implies the 'command' parameter, but gives no meaning for 'cwd', 'timeout', or 'background'. The agent is left to guess their purpose.

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 clearly states the tool's function: 'Execute ANY command on the Kali server without restrictions. Full root access.' It uses a specific verb ('Execute') and resource ('Kali server'), and the scope ('ANY command', 'Full root access') distinguishes it from more specialized sibling tools like nmap or sqlmap.

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 no guidance on when to use this tool versus alternatives. It does not mention any exclusions or specific scenarios, leaving the agent to infer that it is a general-purpose execution tool.

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