Venice Web Scrape

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does mention the firecrawl-default operator preference and x402 wallet auth (no Venice account needed), which is useful. However, it doesn't disclose that this is a read-only operation, what happens on failed scrapes, or the output format beyond 'markdown text'. The description covers auth but lacks depth on failure behavior and 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 compact at three sentences, front-loading the core purpose first. The second sentence ('One URL → markdown text') is somewhat redundant with the first but reinforces scope. No padding or wasted words.

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?

This is a fairly simple tool with only 2 parameters and no output schema, so completeness requirements are moderate. However, with 0% schema coverage, the description should explain the format parameter options (html, text) and disclose behavioral traits for a network-fetching tool (read-only, auth, failure modes). It covers auth but leaves format semantics and error behavior undocumented.

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 parameter documentation. The description covers the 'url' parameter implicitly (one URL) and mentions format output (markdown) but doesn't explain the 'format' enum options (html, text) or what the firecrawl-default operator preference means for format selection. The description adds minimal value over 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 clearly states the tool converts one URL into markdown text, which distinguishes it from its sibling tools like venice_web_search (searching vs. scraping) and venice_text_parser (parsing existing text vs. fetching a URL). The verb+resource (scrape one URL) is specific and clear.

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 notes the operator preferences default (firecrawl-default), which is useful context. However, it doesn't explicitly state when to use this tool vs. alternatives like venice_web_search or discuss limitations (e.g., which URLs work, rate limits). The 'one URL' constraint implies single-page scraping but no exclusions or alternative guidance is given.

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