kali_execute_command

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

With no annotations, the description carries the full burden of behavioral disclosure. It does add useful context about the timeout terminating the command and the default working directory, but for an arbitrary shell execution tool it omits important traits: it does not mention that commands can mutate the host filesystem or system state, what happens on non-zero exit codes, whether output is captured and returned, or what privileges the command runs with.

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 compact and front-loaded with a one-sentence purpose followed by a clean parameter list. Every sentence adds meaningful information, and there is no filler or redundant restatement.

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 description covers the basic invocation details for all three parameters, and an output schema exists so return-value documentation is less critical. However, for a dangerous raw shell execution tool with no annotations, the description remains incomplete because it lacks guidance about side effects, command failure behavior, and how this tool relates to the specialized Kali sibling tools.

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?

The input schema has no descriptions, so the description compensates well by explaining all three parameters, giving defaults for timeout_seconds and cwd, and providing a realistic command example. However, the stated cwd default './kali_workspace' conflicts with the schema's default of null, which introduces ambiguity and prevents a perfect score.

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 verb 'executes' and the resource 'shell command on the Kali Linux host system', with concrete examples like 'nmap -sS 192.168.1.1'. However, it does not explicitly distinguish itself from sibling specialized tools such as kali_run_nmap or kali_run_sqlmap, and the example commands actually overlap with those tools, so it stops short of a 5.

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 prefer this generic executor over the specialized sibling tools. The description even gives 'nmap' and 'nikto' as examples, which could mislead an agent into using this tool instead of kali_run_nmap or other dedicated wrappers. No when-to-use or when-not-to-use conditions are provided.

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