websex_theharvester

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 disclose two meaningful behaviors: the container executes theHarvester directly with supplied argv tokens and 'shell parsing is never used' (an injection-relevant safety trait), plus the engagement-namespace scoping. It stops short of stating network access, rate/scope limits, or output side effects, so it is useful but incomplete for an execution wrapper.

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 tight sentences, front-loaded with the action, then execution semantics, then scoping. No filler. Slightly terse given the 4 undocumented parameters, but no sentence is wasted.

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 needn't be explained, and the description covers execution mode and namespace scoping. But for a no-annotation shell-execution wrapper with 0% parameter coverage, an agent still lacks argument examples/format and any statement of network or permission requirements. Adequate, not 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%, so the description must compensate. It clarifies that 'arguments' are argv tokens passed verbatim (not a shell string), that paths are relative to the engagement namespace (implying engagement_id/working_directory semantics), but it never mentions the 'stdin' parameter at all. Partial compensation for 3 of 4 params.

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 and resource: 'Run theharvester from the WebSex enumeration toolkit.' An agent knows exactly what gets executed. However, it never distinguishes theHarvester from the many OSINT/recon siblings (amass, subfinder, fierce, dnsenum, spiderfoot), so the 'why this one' is left to outside knowledge.

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?

Gives operational context — 'Runs from the selected engagement namespace; use relative paths for engagement artifacts' — which tells the agent how to scope the invocation, but no when-to-use/when-not guidance and no alternative tool named. Usage is implied rather than directed.

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