kali_enumeration_tools

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to describe any behavioral traits such as whether it's read-only or destructive, what permissions are needed, rate limits, output format, or error handling. For a tool with potential security implications (enumeration), this is a critical gap.

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 a single phrase 'Enumeration and service detection tools', which is appropriately sized and front-loaded. It wastes no words, though it could be more informative. However, it lacks structure (e.g., no separation of purpose from usage).

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 complexity (enumeration tools in a security context), no annotations, no output schema, and 3 parameters, the description is incomplete. It doesn't explain what the tool does operationally, what to expect as output, or any behavioral constraints. For a tool in this domain, more detail is needed to guide safe and effective use.

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 the schema already documents all parameters (tool, target, options) with descriptions. The description adds no additional meaning beyond what's in the schema, such as examples of tools or common options. With high schema coverage, the baseline is 3, as the description doesn't compensate but doesn't detract either.

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 'Enumeration and service detection tools' states a general purpose but lacks specificity. It mentions the category of tools (enumeration/service detection) but doesn't specify what actions are performed (e.g., scanning, querying, analyzing) or what resources are targeted. It distinguishes somewhat from siblings like 'kali_network_scan' or 'kali_service_scan' by focusing on enumeration, but the distinction is vague.

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 is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context (e.g., for reconnaissance phases), or comparisons to siblings like 'kali_network_scan' or 'kali_service_scan'. It leaves the agent to infer usage based on the tool name alone.

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