pentest_recon_tech

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 usefully discloses that detection draws on both headers and body, implying an active HTTP fetch of the target, but says nothing about redirect handling, authentication needs, request volume, or what the result looks like.

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 well-formed sentence with the action and data sources front-loaded and no filler. Every clause earns its place.

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 simple single-parameter tool with no output schema, the description explains what is fingerprinted and from what evidence, but omits what the return value contains (detected technologies, versions, confidence) and any scope-check prerequisite. Adequate but with clear gaps.

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?

Only one parameter with 0% schema description coverage, so the description must compensate. It adds the meaningful constraint that the URL must be in engagement scope, but gives no format guidance (scheme, host vs full path) beyond that.

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 ('Fingerprint') and resource ('technology stack of an in-scope URL') and even names the evidence sources (headers, response body). This distinguishes it from pentest_web_headers, which only dumps headers, though it never explicitly names the sibling.

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 'in-scope URL' implies a scope prerequisite and hints at reconnaissance usage, but there is no explicit when-to-use vs alternatives guidance (e.g. vs pentest_web_headers or pentest_assess_web). Usage must be inferred from the name and prefix.

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