scrape_with_stealth

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does describe key behavioral traits: 'advanced stealth techniques,' 'anti-detection methods,' and lists specific techniques like undetected browser automation and randomized patterns. However, it lacks details about potential risks, rate limits, authentication needs, or what happens when detection occurs.

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?

The description is appropriately sized with clear front-loading of the main purpose. The bullet-point list of techniques is organized and adds value. However, the final usage guideline sentence could be more integrated with the opening statement for better flow.

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?

Given the complexity of stealth web scraping (which involves evasion techniques and potential ethical/legal considerations), the description is moderately complete. It covers the 'why' (anti-bot protection) and 'how' (stealth techniques) but lacks details about parameters, output format (though output schema exists), error conditions, and limitations. The presence of an output schema helps but doesn't compensate for missing behavioral context.

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 the description must compensate for undocumented parameters. The description mentions 'stealth techniques' and 'anti-detection methods' but provides no information about the actual parameters (url, method, scroll_page, wait_for_element, extract_config). It doesn't explain what these parameters mean or how they relate to the stealth functionality.

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 clearly states the tool's purpose as 'Scrape a webpage using advanced stealth techniques to avoid detection,' which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'scrape_webpage' or 'scrape_multiple_webpages' beyond mentioning stealth techniques for anti-bot protection.

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 description provides clear context for when to use this tool: 'Use this for websites with strong anti-bot protection.' This gives practical guidance about the target scenario. However, it doesn't explicitly state when NOT to use it or mention specific alternatives among the sibling tools.

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