kali_exec

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

With no annotations provided, the description carries the full burden of behavioral disclosure. For a tool that executes arbitrary shell commands, it fails to mention safety implications, environment specifics, whether the container is ephemeral, or what the output/return behavior is. The description only states the environment (Kali Docker container) without addressing the potentially destructive nature of running arbitrary commands.

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 exceptionally concise: two sentences with no redundant words. The first sentence states the action and target, the second provides usage guidance. Every word earns its place, and the structure is well front-loaded.

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?

The tool has one parameter and no output schema, so the description is reasonably complete for a straightforward execution tool. However, it omits any mention of what the command's output looks like or whether it returns results, which is a meaningful gap for a shell execution tool. The behavioral transparency deficit also affects completeness.

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%, with the single 'command' parameter already having a clear description and example. The tool description itself adds no additional parameter semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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 runs an arbitrary shell command inside the Kali Docker container on Draydev, which is a specific verb+resource combination. It also distinguishes itself from sibling tools by explicitly saying 'Use for tools not covered by other kali_* tools', making the purpose unambiguous.

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 a clear usage guideline: use it for tools not covered by other kali_* tools, implying that specialized sibling tools should be preferred when they apply. It doesn't explicitly state exclusions for specific tools, but the context of sibling tools like kali_nmap and kali_web_scan makes the intended use clear.

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