websex_subfinder

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

With no annotations, the description carries the full burden, and it does add real value: it discloses that argv tokens are passed directly with no shell parsing (relevant for quoting/injection behavior) and that execution happens in the selected engagement namespace with relative artifact paths. It omits safety/network profile (read-only vs. state-changing), rate/timeout behavior, and failure modes.

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 compact sentences, front-loaded with the core action (run subfinder) followed by execution semantics. No filler or repetition, though the three sentences are somewhat heterogeneous in topic rather than tight to one purpose.

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 execution model is covered. However, for a four-parameter wrapper with zero schema coverage and no annotations, the description leaves parameters and the safety profile underspecified; it is minimally adequate rather than complete.

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% across four parameters, and the description only indirectly gestures at them: 'supplied argv tokens' hints at arguments, 'selected engagement namespace' at engagement_id, and 'relative paths for engagement artifacts' at working_directory. The stdin parameter is entirely undocumented in both schema and description, leaving a real gap.

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?

States a specific verb+resource ('Run subfinder') and identifies it as part of the WebSex enumeration toolkit, so an agent knows it invokes the subfinder binary rather than a sibling. It does not, however, differentiate the tool from near-neighbors like websex_amass or websex_fierce, and it never states what subfinder actually produces (subdomain enumeration), relying on the agent's prior knowledge of the binary.

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 operational context (engagement namespace, relative paths) but no when-to-use/when-not-to-use guidance and no mention of alternatives, despite many siblings in the same subdomain/DNS enumeration space (amass, fierce, dnsenum, theharvester, subzy). The agent must infer selection criteria on its own.

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