kali_social_engineering

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. 'Social engineering tools' gives no indication of what the tool actually does behaviorally—whether it runs commands, installs packages, launches interfaces, or performs other operations. It doesn't mention permissions needed, side effects, or output characteristics.

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?

While concise with only two words, this is a case of under-specification rather than effective brevity. The description fails to convey essential information and doesn't front-load key details about the tool's function, making it inefficient despite its short length.

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 implied by the tool name (potentially involving multiple sub-tools like setoolkit and king-phisher), lack of annotations, no output schema, and sibling tools indicating a Kali Linux security context, the description is completely inadequate. It doesn't explain what the tool returns, how it behaves, or its role within the toolset.

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%, with both parameters ('tool' and 'options') fully documented in the schema. The description adds no additional meaning beyond what's already in the schema (e.g., examples of tools, typical options). With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 'Social engineering tools' is a tautology that essentially restates the tool name 'kali_social_engineering'. It lacks a specific verb indicating what action this tool performs (e.g., 'run', 'configure', 'launch') and doesn't distinguish it from sibling tools like 'kali_enumeration_tools' or 'kali_web_exploitation' beyond the general category name.

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 provides no guidance on when to use this tool versus alternatives. There are no explicit or implied instructions about appropriate contexts, prerequisites, or comparisons to sibling tools like 'kali_web_exploitation' or 'kali_information_gathering' that might overlap in ethical hacking domains.

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