parse_nuclei_output

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

With no annotations, the description is the sole source for behavioral transparency. It discloses the file source and the act of parsing, but it omits details about side effects, error handling, or the exact structure of the output. Since this is a read-only parsing operation, the omission is not critical, but more specifics on the return format would have improved transparency.

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 two focused sentences: one for the purpose and one for the parameter. Every word earns its place, with no fluff or repetition of the tool name. It is appropriately front-loaded and minimal.

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?

For a simple one-parameter parser without an output schema, the description covers the input and its origin well. It could be improved by describing the output structure or error behavior, but given the tool's simplicity and the clarity of the pipeline context, it is nearly 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?

The schema offers no description (0% coverage), yet the description fully compensates with a precise sentence: 'findings_file: path returned by nuclei_scan as findings_file.' This explains exactly what the parameter is, its type, and where to obtain it, leaving no ambiguity for the sole parameter.

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 uses a specific verb 'Parse' and specifies the resource 'nuclei JSONL findings file' and the outcome 'structured vulnerability data'. It distinguishes from sibling tools like nuclei_scan by focusing on parsing, and mentions the specific format, making it unambiguous.

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 clarity by stating the findings_file is the path returned by nuclei_scan, directly tying this tool to the post-scan workflow. However, it does not explicitly mention any alternatives (e.g., parse_nmap_output) or when not to use it, so it falls short of a 5.

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