pentest_ctf_web_probe

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

No annotations are supplied, so the description carries the entire behavioral burden, yet it says nothing about side effects. For an active exploitation tool that sends SSTI/LFI/injection payloads, an agent needs to know noise level, whether requests could mutate target state, and whether errors abort the run — none of which is disclosed. The engagement prerequisite is the only extra context offered.

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?

Two short, front-loaded sentences with no filler; the probe classes come first and the prerequisite last. It is terse rather than padded, though the terseness contributes to the specification gaps noted elsewhere.

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 two-parameter CTF helper with no output schema or annotations, the description establishes what it targets and the engagement prerequisite, which is enough to attempt a call. It is still missing how probe modes are chosen and what a response contains.

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% for both parameters. The description does not explain what `url` should point at (endpoint vs parameter URL) nor what the `params` array represents — injectable parameter names, payloads, or probe selectors — which is exactly the ambiguity an agent would hit at call time.

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 resource family — SSTI evaluation, LFI traversal, and command-injection echo — which tells an agent the exact vulnerability classes the tool exercises, clearly distinguishing it from the generic web tools like pentest_web_sqlmap or pentest_web_reflection. The action verb 'probes' is somewhat soft, but combined with the three named techniques it is concrete enough to identify the tool.

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?

'Requires a loaded engagement' states a prerequisite rather than when to use this versus alternatives. There is no guidance on whether the tool runs all three probe types at once or how to select one, and no explicit exclusion against siblings such as pentest_web_reflection or pentest_assess_web.

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