websex_rustscan

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

With no annotations, the description carries the full behavioral disclosure burden. It usefully explains that the container executes rustscan directly with argv tokens and never uses shell parsing, and that it runs from an engagement namespace with relative paths. It omits operational safety details such as intrusiveness, permissions, or side effects for a network scanning tool.

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 three short sentences with the purpose front-loaded and no wasted words. It is appropriately sized for the tool and delivers execution details efficiently.

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?

An output schema exists, so return values need not be described. However, for a command-execution tool with four parameters and 0% schema description coverage, the description leaves engagement_id and stdin unexplained and omits safety or side-effect context. It is adequate but incomplete.

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%, so the description must compensate for four undocumented parameters. It partially does: 'supplied argv tokens' clarifies the arguments array, 'relative paths' relates to working_directory, and 'engagement namespace' hints at engagement_id. It never mentions stdin or fully specifies any parameter.

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 rustscan from the WebSex network toolkit.' This clearly identifies the tool's action and the underlying binary. However, it does not differentiate rustscan from sibling scanners such as nmap, masscan, or autorecon.

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 explicit when-to-use guidance, no alternatives, and no exclusions. It mentions running from an engagement namespace and using relative paths, but that is execution context rather than guidance on when this tool is appropriate versus its siblings.

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