websex_amass

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

With no annotations, the description carries the full burden. It usefully discloses that arguments are passed as argv tokens with shell parsing never used (so no shell expansion/injection semantics) and that it runs from the engagement namespace. It does not state permissions, network behavior, or whether the operation mutates anything, which is a gap for an unannotated execution 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?

Three short sentences, front-loaded with the action, and each adds a distinct piece of information about execution or path handling. No filler.

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 no explanation, and the execution model (argv, cwd, namespace) is covered. However, the 0%-documented stdin parameter and the absence of any indication of what amass actually enumerates leave an agent with gaps for a 4-param execution wrapper.

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 4 params, so the description must compensate. "Supplied argv tokens" maps to the arguments array, "runs from the selected engagement namespace" hints at engagement_id, and "relative paths for engagement artifacts" hints at working_directory. The stdin parameter is left entirely unexplained, so compensation is only partial.

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 amass from the WebSex enumeration toolkit"), which tells an agent this is a subdomain/enumeration wrapper. It doesn't differentiate from siblings like websex_subfinder, websex_dnsenum, or websex_theharvester, so the agent still has to know what amass does versus those tools.

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 instructions ("runs from the selected engagement namespace", "use relative paths") but no guidance on when to choose amass over the many sibling enumeration tools. There is no when-to-use, no exclusions, and no named alternative.

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