pentest_report

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

No annotations are provided, so the description carries the full behavioral burden. It implies a file write into an evidence directory but says nothing about whether existing output is overwritten, whether the directory must already exist, what source data (findings/engagement) gets rendered, or whether prerequisites must be met first.

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?

A single front-loaded sentence with no wasted wording. It is arguably too terse rather than bloated, but structurally it is clean and readable.

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 one-optional-parameter rendering tool with no output schema, the description still leaves real gaps: no indication of which data is rendered, where output goes by default, or how it differs operationally from the html/sarif/generic_json report tools. Given the tool's low complexity, these are meaningful omissions rather than fatal ones.

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 coverage is 0% for the single optional parameter, and the description does not explain what output_path means – whether it is a file name, an absolute path, or a path relative to the evidence directory, nor what happens when it is omitted (the schema default is an empty string). The mention of 'evidence directory' gives only a weak hint about the default destination.

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 names a specific verb and resource ('Render the Markdown engagement report') and adds a destination ('into the evidence directory'), which implicitly distinguishes it from the sibling report tools (pentest_report_sarif, pentest_report_html, pentest_report_generic_json). It does not explicitly name those siblings, so an agent still has to infer the format split rather than being routed.

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?

There is no when-to-use or when-not-to-use guidance, and no alternatives are named despite four closely related report-rendering siblings. The intended position in the workflow (presumably after findings are collected) is left entirely to inference.

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