kali_get_tool_help

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

With no annotations provided, the description carries the full burden. It transparently states that the tool retrieves documentation rather than executing the target tool, which implies a read-only, non-destructive operation. This is adequate for a simple help-retrieval tool, though it does not discuss edge cases like unavailable tools.

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 and front-loaded with the core purpose in the first sentence. The Args section adds necessary parameter context without redundancy or filler.

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 single-parameter, read-only help tool with an output schema, the description provides enough information to select and call it. It could be slightly stronger with explicit guidance about when to use it relative to the specialized run_* siblings, but overall it is complete.

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 schema provides no description for tool_name, but the tool description compensates by defining it as the binary utility name and giving concrete examples ('nmap', 'sqlmap', 'john', 'aircrack-ng'). This is sufficient for correct invocation.

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 the tool retrieves manual or --help documentation for any Kali Linux tool, which is a specific verb and resource. It is distinguishable from siblings like kali_execute_command and kali_run_nmap, though it does not explicitly name an alternative.

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 phrase 'for any Kali Linux tool' implies this is the general-purpose help tool, distinct from the specialized run_* commands and the search tool. However, it does not explicitly state when to prefer this over siblings or when not to use it.

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