pentest_web_secrets_scan

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

With no annotations, the description carries the full burden. It does disclose two useful traits beyond the name: the scan follows linked resources (so it makes outbound fetches beyond the given URL) and returned secret values are redacted. It omits scope/authorization requirements, whether it respects engagement scope policy, and any depth or rate considerations.

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 front-loaded sentence with no filler; the parenthetical about redaction is well placed. It is efficient, though its brevity is partly the source of the semantic gaps rather than a virtue in itself.

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 fetching tool with no annotations and no output schema, the description says nothing about what a finding looks like, where results are reported (e.g., whether it auto-adds to pentest_list_findings), or what the crawl limit changes. An agent could invoke it, but not confidently predict scope or output.

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, so the description must compensate and largely does not. It never references 'url' format expectations or explains that 'max_resources' caps how many linked resources are crawled (only implied loosely by 'linked resources'), leaving the default of 10 and its trade-offs undocumented.

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 (scan) and a specific resource set (a page plus its linked resources) with a named target class (credential material). That distinguishes it from most siblings, though it does not explicitly separate it from the similarly-scoped pentest_osint_js_secrets.

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 mention of alternatives such as pentest_osint_js_secrets for JS bundles or pentest_web_crawl for discovery. The agent must infer the trigger conditions and any prerequisite scope check itself.

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