enum4linux_scan

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

With no annotations, description must disclose behavior. It details execution timing but does not explain the scan's nature (e.g., read-only, network scanning, potential side effects). Missing core operational context.

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?

Short but inefficient; focuses on a secondary aspect (timing) while ignoring primary purpose. Not well-structured for quick agent comprehension.

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 7 parameters, 0% schema coverage, and presence of output schema, the description is grossly incomplete. Agent lacks info to set parameters correctly or understand return values. Outside timing, the tool is undefined.

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 coverage is 0%, so description must cover parameters. It only discusses timing-related parameters (on_timeout, timeout_seconds, etc.) but omits 'target' (required), 'additional_args', and others. No semantics for the most critical parameter.

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?

Description omits what enum4linux_scan does. It only mentions 'Kali Agent MCP tool' without specifying that enum4linux enumerates Samba/Windows shares. The verb and resource are missing, making it unclear to an agent unfamiliar with enum4linux.

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?

No guidance on when to use this tool vs. siblings like nmap_scan, nikto_scan, or dirb_scan. Only timing guidance for on_timeout is provided, which is insufficient for tool selection.

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