websex_netbios_scan

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

With no annotations, the description carries the full behavioral burden. It discloses useful execution details: the container runs `nbtscan` directly with argv tokens and never uses shell parsing, and it runs from the selected engagement namespace using relative paths. However, it does not state whether the scan is read-only/non-destructive, what permissions or network impact it has, or expected runtime, leaving key behavioral traits undisclosed.

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 short and front-loaded, leading with the tool's purpose and then briefly covering execution and namespace/path behavior. Every sentence carries relevant information, though it could be slightly more explicit about parameter semantics without becoming verbose.

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 scan-execution tool with no annotations, no schema descriptions, and four parameters, the description is incomplete. It omits parameter-level details, safety/impact information, and when-to-use guidance against sibling tools. The output schema exists, so return value explanation is not required, but the description remains insufficient for confident invocation.

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 0% for four parameters, so the description must explain the parameters. It only indirectly references `arguments` via 'supplied argv tokens', `engagement_id` via 'selected engagement namespace', and `working_directory` via 'relative paths'. The `stdin` parameter is never mentioned, and no parameter format or syntax is clarified. Compensation is insufficient.

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 states a specific verb and resource: 'Run netbios scan' using the `nbtscan` tool. This clearly distinguishes it from broad network scanners like nmap or rustscan, and from SMB enumeration siblings. An agent can identify the tool's core purpose immediately.

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 gives no guidance on when to use this tool versus alternatives such as enum4linux, nmap, or smbmap. It only states that it runs from the engagement namespace and to use relative paths, which is operational context rather than selection guidance. No prerequisites or exclusions are provided.

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