websex_autorecon

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that the container executes autorecon directly with argv tokens and that shell parsing is never used (an injection/quoting-relevant detail), plus that it runs from the engagement namespace with relative paths. It omits permissions, runtime duration, and network-impact caveats for an active scanner.

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?

Three sentences, front-loaded with the purpose and followed by execution semantics; no filler. It is appropriately sized, though it could tie the operational notes more tightly to the argument/namespace parameters.

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 explained, and the description covers the key execution semantics an agent needs. Still, for an active recon tool with zero annotations it could say more about scope/permissions and the undocumented stdin parameter.

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 coverage is 0%, so the description must compensate for four undocumented parameters. It clarifies that 'arguments' are raw argv tokens passed without shell parsing and that relative paths apply to engagement artifacts (working_directory/engagement_id), but it says nothing about 'stdin', leaving one parameter with no semantic guidance anywhere.

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 autorecon from the WebSex network toolkit'), so an agent immediately knows this invokes the autorecon orchestrator. It does not, however, position itself against the many sibling recon tools (nmap, rustscan, masscan) that could also be chosen.

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?

Usage is only implied by the tool name: run automated recon via autorecon. There is no explicit when-to-use/when-not or routing to alternatives like nmap or rustscan, though the note about running from the engagement namespace offers some operational context.

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