zebbern_exec

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

With no annotations, the description adequately discloses full root access, no timeout limits (default 1 hour), return format, and fire-and-forget behavior. It does not mention danger or side effects, but the 'without restrictions' statement provides openness.

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 concise (3 sentences plus bullet-like args and returns). It could be more structured with explicit sections, but remains clear and free of fluff.

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 output schema exists (though not shown), the description covers all necessary aspects: purpose, parameters, return values, and behavior. For a generic execution tool, this is complete and sufficient.

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 0% parameter descriptions, so the description carries full burden. It explains each parameter (command: any shell command; timeout: default 3600; cwd: optional directory; background: fire-and-forget with task_id), adding significant value 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?

The description clearly states it executes any command on the Kali server with root access and no restrictions. It is distinct from sibling tools which are specific (e.g., nmap, hydra), leaving no ambiguity about its generic purpose.

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 implies this tool is for raw command execution when specific tools are not appropriate. However, it does not explicitly state when to use or avoid this tool versus alternatives, nor does it mention prerequisites.

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