pentest_vuln_sslscan

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

No annotations are supplied, so the description carries the full burden. It does disclose the external-binary dependency ('requires sslscan'), which is genuinely useful, but says nothing about intrusiveness/active-connection behavior, expected runtime, whether it is safe or non-destructive, or what happens on failure. For an active network scanner with zero annotation coverage, this is a significant gap.

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 sentence, front-loaded with the action and tool name, followed by the scan scope and the prerequisite. Nothing is wasted and there is no filler prose.

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 single-parameter wrapper with no output schema, the description covers what the tool does and one prerequisite, but omits return format (no output schema exists to compensate), sibling differentiation against testssl/tls, and runtime expectations. It is minimally sufficient but leaves real gaps for an agent choosing between TLS scanners.

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%, so the description must compensate for the single 'target' parameter. It adds that the target is an in-scope host, which is meaningful scoping information, but gives no format guidance (hostname vs IP vs host:port vs URL) and no example, leaving the caller to guess the accepted syntax.

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 tool ('Run sslscan') plus the resource class targeted ('cipher/certificate weaknesses') and the target type ('in-scope host'). It does not distinguish itself from the very similar siblings pentest_vuln_testssl and pentest_vuln_tls, so an agent cannot tell which TLS scanner to pick from the description 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?

The phrase 'against an in-scope host' implies usage context (scope validation before running, presumably via pentest_scope_check), and '(requires sslscan)' warns of an environmental prerequisite. However, there is no explicit when-to-use vs the alternative TLS scanners, and no when-not-to-use guidance (e.g., non-TLS services).

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