zebbern_exec

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 discloses full root access, unrestricted execution, default timeout behavior, return fields, and background-mode behavior. This gives the agent a clear picture of what happens before, during, and after the call.

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 tightly structured with an opening summary followed by Args and Returns sections. Every sentence adds value, and the most important scoping information is front-loaded. 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?

For a 4-parameter arbitrary command execution tool, the description covers behavior, parameters, return shape, and background execution adequately. It also has an output schema available, and the description complements it by explaining what background mode returns.

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?

Input schema has 0% description coverage, but the tool description fully compensates by explaining every parameter: command supports pipes/chains, timeout default is 3600 seconds, cwd sets the working directory, and background returns a trackable job_id. This is exactly the semantics an agent needs beyond the bare schema.

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?

States a specific verb and resource: 'Execute ANY command on the Kali server without restrictions.' The phrase 'Full root access' makes the scope and privilege level unambiguous. It clearly differentiates this generic raw-execution tool from specialized sibling tools like tools_nmap or reverse_shell_command.

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 clearly establishes that this is the go-to tool for arbitrary shell commands on the Kali server, with no explicit exclusions. It does not name alternatives such as exec_stream or ssh_session_command, but the 'ANY command' framing provides strong contextual guidance for when to use it.

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