pentest_vuln_testssl

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

No annotations are provided, so the description carries the full burden. It does disclose an external dependency (testssl.sh or testssl must be installed), which is useful, but says nothing about runtime cost (testssl audits are slow), targeting constraints, or what a run produces. That leaves an agent guessing about behavior for an unannotated 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?

One compact sentence with no filler, and the tool name and purpose are front-loaded. It is lean to the point of being under-specified, 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?

With no annotations, no output schema, no parameter documentation, and no differentiation from TLS siblings, the definition is too thin for an agent to invoke it confidently. It should at minimum define the target format and the expected result shape.

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% and the single required 'target' parameter is completely undocumented. The description does not clarify whether target is a hostname, host:port, or full URL, nor whether a scheme/path is accepted — exactly the gap the description should fill for a CLI-backed tool.

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 testssl.sh for a deep TLS/cipher audit'), which is clear on its own. However, it never distinguishes itself from sibling tools pentest_vuln_sslscan or pentest_vuln_tls, which plausibly audit the same surface, so an agent cannot choose between them from this text alone.

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 guidance and no exclusions. The closest thing is the implicit hint that this is a 'deep' audit, but with two TLS-audit siblings listed there is no stated condition for picking this one over sslscan or tls.

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