shell_exec

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

No annotations are provided, so the description must carry the full behavioral burden. It adds a warning that this is an escape hatch and should be avoided when dedicated tools suffice, which is useful context. However, it does not disclose critical behavioral traits for arbitrary shell execution, such as privilege level, potential destructiveness, reversibility, or output handling, leaving significant gaps.

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 two tight sentences with zero waste, front-loading the core action and following immediately with the critical usage warning and restriction. Every sentence earns its place.

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 high-complexity tool like arbitrary shell execution with no annotations and no output schema, the description covers purpose and usage guidance well. However, it does not explain return values, error behavior, or execution context (e.g., whether output is captured, how errors are surfaced), which an agent would need to call it correctly without an output schema.

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%, so both parameters ('command' and 'timeout_ms') are already well documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, so the baseline 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 states a specific verb ('Execute') and resource ('arbitrary shell command on the remote Kali Linux machine'), and it distinguishes itself from the many specific scanning siblings by framing itself as an escape hatch to be used only when dedicated tools don't cover the need. An agent can immediately tell what this tool does and when it is appropriate.

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 explicitly tells the agent when to use this tool ('escape hatch for advanced scenarios', 'commands not covered by dedicated tools') and when not to ('prefer specific tools'). The alternative is named as a category ('specific tools') even if individual siblings aren't listed, which is sufficient to route correctly given the sibling set is visible elsewhere.

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