pentest_exploit_credential_test

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

With no annotations, the description carries the full burden and does real work: it discloses the authorization gate, the confirmation-phrase check, the input size ceiling, and that discovered passwords are redacted in output. It omits operational risk context an agent would want, such as account lockout potential or rate limiting on the target service.

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?

Three short sentences, front-loaded with the action and cap, followed by the gate and the output caveat. Nothing is redundant and no sentence could be dropped without losing required information.

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 gated, no-annotation, no-output-schema security tool this covers the essentials — authorization, sizing, and output redaction — but leaves gaps on target/port semantics and supported service values that an agent needs before calling. Adequate rather than 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?

Schema coverage is 0% across 6 parameters, so the description must compensate. It gives meaning to users/passwords (bounded lists), service ('one service'), and confirm_phrase (must equal engagement_id), but leaves target format and especially port unexplained — the port default of 0 is ambiguous with no hint whether 0 means auto-select.

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 ('Test a small credential list against one service with hydra') and bounds the inputs ('max 50 users / 50 passwords'). No sibling tool in the list performs credential testing, so the agent can distinguish this from pentest_exploit_search or pentest_exploit_msf_run purely from the text.

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?

Preconditions are stated explicitly: rules.credential_testing must be true and confirm_phrase must equal the engagement_id, plus the 50/50 size cap that steers larger jobs elsewhere. It does not name an alternative tool for large lists or state when not to use it, so it stops short of full routing guidance.

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