websex_fierce

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 real behavioral traits: execution is argv-based with 'shell parsing is never used' (an injection-safety fact), and the process runs from the engagement namespace. It omits network egress implications, expected runtime, and what the tool targets. Useful context but incomplete for a command-execution tool with zero annotation coverage.

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 with the action front-loaded and no filler. Each sentence adds something (what runs, how it runs, where it runs). Slightly more could be said about the tool's purpose, but nothing 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 need not be explained, which the description correctly omits. But for a 4-parameter tool with 0% schema coverage and no annotations, the description leaves engagement_id and stdin unexplained and gives no sense of what fierce enumerates, so it is only minimally 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 4 parameters, so the description must compensate. It only implicitly touches two: 'supplied argv tokens' maps to arguments and 'relative paths for engagement artifacts' hints at working_directory. engagement_id and stdin are never addressed, leaving half the surface undocumented in both schema and description.

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 fierce from the WebSex enumeration toolkit.' An agent knows exactly which binary will execute. However, it never says what fierce actually does (DNS/subdomain reconnaissance) nor distinguishes it from siblings like websex_dnsenum, websex_amass, or websex_subfinder, so sibling differentiation is absent.

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 only guidance is operational ('runs from the selected engagement namespace; use relative paths'), not selectional. It never says when to reach for fierce instead of dnsenum, amass, or theharvester, nor what conditions make it the right choice. No when/when-not/alternatives present.

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