Extract structured data

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

No annotations are provided, so the description carries the full burden. It discloses billing behavior ($0.01 per record) and failure policy (failures free), which is useful. However, it omits details such as authentication requirements, rate limits, or handling of invalid/unsupported URLs beyond 'failures free'. This is partial transparency.

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 two sentences, front-loaded with the core purpose, and includes only necessary details (pricing, supported scrapers). No redundant words or overly long explanations.

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 tool's moderate complexity (3 params, no output schema), the description covers the essential aspects: source platforms, pricing, failure policy, and available scrapers. It doesn't detail the exact JSON structure per scraper, but the phrase 'ready-made structured JSON' provides sufficient expectation for an agent to select and invoke the tool.

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 coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by clarifying which URLs are eligible (Amazon, Walmart, etc.) and implicitly linking the 'limit' parameter to per-record billing. This helps the agent understand parameter semantics in context.

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 extracts structured JSON from specific platforms (Amazon, Walmart, etc.) with a specific verb 'extract' and resource 'structured data'. It distinguishes itself from siblings like scrape_page and crawl_site by emphasizing 'ready-made' structured output from a curated list of sources.

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 implies when to use the tool: when the URL is from one of the listed platforms and structured data is needed. It lists supported scrapers, effectively setting the inclusion criteria. However, it does not explicitly mention alternatives like scrape_page for unsupported URLs, so it lacks an explicit when-not-to-use statement.

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