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 doesn't disclose that this is a long-running, high-cost operation, rate limiting, permission requirements, or what 'store_data' actually mutates in Spider Cloud – significant gaps for an 18-parameter mutation-capable crawl.

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?

A single front-loaded sentence with no waste, though it is arguably too terse for an 18-parameter tool. Efficient phrasing that earns its place but under-delivers given the complexity.

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 an 18-parameter crawl with no annotations and no output schema, the description covers almost none of what an agent needs: cost/time expectations, parameter interactions, or the effect of store_data. Inadequate for the tool's complexity.

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 reported 0% (raw schema has empty descriptions), so the description must compensate. It mentions 'depth, limits, and filtering options' generically, leaving 15+ parameters – budget, blacklist/whitelist wildcards, stealth/anti_bot, proxy, store_data – completely unexplained.

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 (Crawl) and resource (entire website) and lists the dimensions of configurability. It distinguishes itself from spider_scrape (single page) and spider_search (query-based) by scope, though it doesn't name those siblings explicitly.

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?

Implied usage: crawl an 'entire website' when you need multi-page coverage versus a single scrape. No explicit when-to-use, when-not-to-use, or named alternatives, so the agent must infer routing among the five siblings.

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

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

No annotations are provided, so the description carries the full behavioral burden and mostly fails it. It does not disclose that store_data writes to Spider Cloud, whether proxy_enabled incurs cost or latency, or any rate/limit behavior — all of which matter for an 11-parameter tool.

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?

A single clean sentence is front-loaded and free of waste, but for a tool with 11 parameters it is under-specified rather than genuinely concise; the sentence has no follow-up detail to justify its brevity.

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?

An 11-parameter, no-annotation, no-output-schema tool needs substantially more context than one sentence. Key behaviors — what 'analyze' means, how depth interacts with limit, what store_data persists, what return_format changes — are entirely absent.

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?

With 11 parameters and effectively no substantive description coverage, the description is the only place to add meaning, yet 'with filtering options' names none of the filters (depth, limit, unique, external, subdomains, proxy settings, return_format). The individual schema descriptions exist but are terse one-liners that do not convey interaction or defaults.

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 states a specific verb+resource ('Extract and analyze all links from a webpage'), which is clearly distinguishable from spider_scrape, spider_crawl, and spider_search. The word 'analyze' is vaguer than 'extract,' but the core purpose is unambiguous.

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?

There is no guidance on when to use this tool versus spider_scrape or spider_crawl, both of which also operate on a URL. 'With filtering options' hints at capability but gives no conditions, prerequisites, or alternatives.

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

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no note that premium proxy/stealth modes may carry cost or latency, no authentication or Spider Cloud credential requirement, no rate limits, and no statement of what happens to the page content when store_data persists it remotely. The three 'advanced options' named are capabilities rather than behaviors.

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?

One front-loaded sentence with no filler; the core action leads and the qualifiers follow. It is efficient, though it spends its back half listing three features that the schema already documents, which is space that could have bought usage guidance.

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 16-parameter, no-annotation, no-output-schema tool, this is thin: nothing about the default markdown return, nothing about cost or credential prerequisites, nothing about how it differs from the five sibling tools. An agent can call it, but cannot confidently choose it over spider_crawl or predict what comes back.

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?

The schema itself carries a per-parameter description for all 16 fields (js, anti_bot, css_selector, timeout bounds, return_format default markdown, etc.), so the schema does the heavy lifting even though the reported coverage signal reads 0%. The description adds essentially no parameter meaning beyond echoing the js, anti_bot, and extraction options already named in the schema.

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 states a specific verb+resource ('Scrape content from a single URL') and enumerates the capability areas: JavaScript rendering, anti-bot bypass, content extraction. This separates it from the plural-scope siblings (crawl/search), but it never names those siblings, so an agent must infer the boundary itself.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as spider_crawl for multi-page work or spider_screenshot when an image is wanted. The word 'single URL' is the only implicit routing signal, and it is embedded in the purpose statement rather than framed as a decision rule.

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

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

No annotations are provided, so the description carries the full disclosure burden, yet it only says 'high-quality' and 'customizable'. It omits whether proxies are required for some sites, how rendering/waiting behaves, rate limits, or that output is an image rather than content.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity reflects under-specification rather than disciplined selection of detail.

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 12-parameter tool with no annotations and no output schema, the description is far too thin. It says nothing about proxy usage, timing behavior, or the nature of the returned image, so an agent must infer everything from the schema.

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?

The description adds only the vague phrase 'customizable viewport and options' and explains no parameter. Although the input schema itself carries per-parameter descriptions, the description contributes no semantics beyond it, leaving the description-level meaning at a minimum.

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+resource ('Capture ... screenshots of webpages') with a hint at configurable scope. It is clearly distinct from siblings like spider_scrape and spider_links, though it never names or contrasts them explicitly.

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?

There is no guidance on when to use this versus spider_scrape/spider_crawl, no prerequisites, and no mention of when a screenshot is inappropriate. The only implied usage is taking a visual capture of a page.

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

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

No annotations are supplied, so the description carries the entire burden. It discloses only that page fetching is optional; it says nothing about the fact that store_data writes results into Spider Cloud (a mutating side effect), nor about proxy usage, rate limits, or credential requirements. That is a meaningful gap for a 14-parameter tool.

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?

A single front-loaded sentence with no filler, which is structurally clean. It is arguably under-sized for the surface area it must cover, but there is no verbosity to trim.

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 14 parameters, no annotations, no output schema, and no parameter documentation, one sentence is far short of complete. The agent lacks the information needed to choose between the search, scrape, links, and crawl siblings or to know what the response contains.

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?

With 14 parameters and reported schema description coverage of 0%, the description must compensate, and it does not. The only parameter behavior it touches is fetch_page_content ("optional page content fetching"); geo/language, pagination (start, num, search_limit), tbs, safe, return_format, and the proxy/store flags are all left unexplained.

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+resource ("Search the web") and adds the shape of the result ("Google-like results") plus the optional content-fetch behavior. However it never distinguishes itself from spider_scrape, spider_links, or spider_crawl, so an agent must infer the boundary on its own.

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?

There is no guidance on when to use this tool versus the five sibling tools, and no mention of prerequisites or exclusions. The only usage signal is the phrase "optional page content fetching," which hints at a capability but not a selection criterion.

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

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

With no annotations provided, the description carries the full behavioral burden, yet it discloses only the transformation targets. It does not state that this is a pure, side-effect-free operation, nor does it explain what 'clean', 'readability', or 'formatted output' actually do to the input.

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?

A single front-loaded sentence with no wasted words. It is efficient, though its brevity is partly the cause of the coverage gaps rather than a deliberate trade-off.

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 6-parameter tool with no annotations and no output schema, the description should explain transformation behavior and the optional flags. Instead it only restates the high-level purpose, leaving the agent with no guidance on how the options interact or what the result looks like.

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 reported at 0%, and the description adds no parameter-level meaning. It mentions markdown and text (partially mapping to return_format) but says nothing about the other options (raw, clean_html) or the clean/readability/include_links/include_images toggles.

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 ('Transform'), a specific resource ('HTML content'), and names the output target formats (markdown, text, formatted output). An agent can tell it is a conversion utility, though it never explicitly contrasts itself with siblings like spider_scrape or spider_crawl.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no mention of when it should not be used. The agent must infer that this is for post-scrape content conversion rather than retrieval.

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