nuclei_scan

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

No annotations are provided, so the description carries the transparency burden. It does meaningfully disclose that the tool wraps `nuclei -u <url> -as -json`, parses output into findings, and depends on nuclei being installed. However, it does not mention side effects such as network requests made to the scanned target, runtime expectations, or implications of automatic-scan mode.

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?

The description is very concise and front-loaded: it states the main action first, then provides the exact command behavior, output handling, and a prerequisite. Every sentence contributes useful information with 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?

The tool has a well-covered input schema and an output schema, so the description does not need to repeat parameter or return details. It supplies key external dependency and command-wrapper context. It falls slightly short by not explaining when the agent should use this tool instead of the specialized sibling scan tools.

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?

Since schema description coverage is 100%, the parameter semantics are already well covered by the input schema, giving a baseline of 3. The description only adds context around the `url` parameter and the JSON output behavior, but it does not explain tags, scope filtering, severity filters, or extra_args beyond what the schema already provides.

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 clearly states the tool scans a URL using projectdiscovery/nuclei with automatic-scan. It names a specific verb, resource, and tool, but it does not explicitly distinguish itself from sibling scanners such as sqli_scan, xss_scan, or ssrf_scan.

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 provides no guidance on when to choose this general-purpose nuclei scan over the many sibling scanners. It mentions the prerequisite that nuclei must be installed and in PATH, but that is not sufficient usage guidance.

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