pentest_osint_wayback

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

No annotations are supplied, so the description carries the full behavioral burden. 'Passive' is a genuine and useful disclosure that no traffic is sent to the target, but nothing is said about rate limits, timeouts on large domains, whether the query reaches a third-party API (data exposure), or how results are truncated by the default limit of 500.

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 sentences, zero filler, with the resource front-loaded ahead of the qualifier. The 'Passive.' fragment is terse but earns its place by flagging a safety property. The brevity comes at the cost of substance rather than padding.

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 two-parameter read tool with no output schema and no annotations, the description should still convey roughly what comes back (URLs, timestamps, status codes?) and what 'limit' governs. Neither is addressed, leaving the agent guessing on result shape and truncation behavior.

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 both parameters need explanation here. The description implies a target domain but never says it, and 'limit' (default 500) is not mentioned at all — an agent cannot tell whether it caps results, pages, or snapshots. The description does not compensate for the coverage gap.

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 resource: 'List historical URLs and old artifacts from the Wayback Machine.' That is distinct from the other OSINT siblings (crtsh, shodan, cloud_assets, takeover), so an agent can pick it out without opening the schema. It does not explicitly name an alternative, which keeps it from a 5.

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 only usage signal is the trailing word 'Passive', which hints at non-intrusive recon but gives no when-to-use condition, no prerequisites, and no comparison to adjacent tools like pentest_web_crawl or pentest_osint_crtsh. The agent must infer the scenario entirely.

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