scrape_single_url

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

With no annotations provided, the description carries the full burden. It adds context by stating 'Extraction only' (read-only behavior) and listing the technical methods (JSON-LD, OpenGraph, dynamic JS datasets, DOM selectors, CDN upscalers), which implies JavaScript execution and network requests. It does not mention rate limits or auth, but for a scraping tool with a clear read-only hint, this is meaningful.

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 and front-loaded with the core purpose, followed by brevity in 'when to use', a concrete example, and expected return. Every section earns its place, with no filler or redundancy.

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 output schema exists, return values are covered. The description provides usage context, source of URLs, and technical methods. It lacks error handling details or edge-case behavior, but for a simple scraping tool, it is reasonably complete.

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 does not add meaning beyond the schema; the example call illustrates a valid URL but does not clarify parameter semantics further. The schema already documents each parameter adequately.

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 specific verb 'Extracts' and the resource 'high-resolution product imagery from a single direct product URL', which distinguishes it from sibling tools like search_product_urls that search for URLs. The 'Extraction only' parenthetical further clarifies its scope.

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 'USE THIS TOOL WHEN' section explicitly states the condition: when the user already has an exact product URL. It references search_product_urls as a source, providing context, but does not explicitly name alternatives to use instead when the condition is not met. It is clear but lacks explicit when-not guidance.

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