simulate_evil_twin

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

No annotations are provided, so the description carries full burden. It only lists modes without disclosing whether the tool actually executes attacks, captures credentials, or modifies the environment (e.g., it says 'design captive portals' but not if it creates files or connections). The behavioral impact is unclear.

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?

Two sentences; the first sentence repeats 'Evil Twin attack planning and defense' which is redundant. It could be more concise by merging. However, it front-loads the purpose and enumerates modes, so it is structurally adequate but not optimal.

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?

With no output schema, the description should explain what the tool returns, but it does not. Given the complexity of 4 modes and 9 parameters, the description is incomplete—it omits return values, side effects, and prerequisites, making it hard for an agent to use correctly without additional knowledge.

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 each parameter having a brief description in the schema. The tool description groups parameters by mode (e.g., 'target_ssid' for plan mode) but does not add meaning beyond what the schema provides. Baseline 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 clearly states the tool's purpose: 'Evil Twin attack planning and defense. Plan attacks, configure EAP credential capture, design captive portals, generate detection rules.' It specifies the verb (simulate/plan) and resource (evil twin attacks) and distinguishes from siblings like scan_wifi_networks or analyze_wifi_security which are more about reconnaissance.

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 lists four modes but does not provide guidance on when to use this tool versus the many sibling tools (e.g., when to simulate vs. scan or analyze). No explicit context for decision-making is given, leaving the agent to infer usage from the mode list.

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