AI Scraper

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

Annotations are not provided, so the description carries full responsibility. It discloses execution_mode behavior (sync vs async), explains that async returns a request id for polling with requests_get, and describes how schema shapes the output. This is substantive, but it does not address failure modes or rate limits.

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 well-structured with headers ('Best for', 'How schema works', 'Execution notes') and leads with purpose. The example schema JSON is informative and earns its place, though it does lengthen the description slightly.

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 tool with nested schema and 5 parameters, the description covers schema semantics, execution modes, and the combined use of prompt and schema. An output schema is present, so return value details are not necessary. Minor gaps like page size limitations exist but do not undermine completeness.

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 100%, so the baseline is 3. The description exceeds this by explaining execution_mode values (sync/async) and providing a detailed schema example with type, properties, and required guidance, adding meaning beyond the raw parameter descriptions.

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 opens with a specific verb and resource: 'Extract structured information from a web page with Outscraper AI Scraper.' It further clarifies scope with 'Best for scraping one page and turning it into structured JSON' and explicitly distinguishes from sibling tools by stating it is best for structured data from a single page.

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 'Best for' section lists clear use cases, and the description states 'This tool is best for extracting structured data from a single page.' It does not explicitly name alternative tools or state when not to use it, but the context is strong and unambiguous.

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