Venice Web Scrape

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely useful context the annotations do not: dual auth via x402 wallet (no Venice account required) or API key. It does not disclose failure behavior 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?

Two short sentences with no filler, and the core action is front-loaded before the auth detail. Efficient, though it could have folded in the format options at no extra length.

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 two-parameter scrape tool with no output schema, the auth disclosure is a real plus, but the description omits the non-markdown output formats, error/rate-limit behavior, and any note on external-resource variability implied by openWorldHint=true. Adequate but with clear gaps.

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 carry the parameter burden. It only mentions markdown output, which corresponds to one enum value, and says nothing about the html/text alternatives the format parameter offers, nor any constraints on the URL. The url parameter is self-evident but format is under-explained.

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 (Scrape) and resource (one URL) plus the output form (markdown text). The word 'one' implicitly distinguishes it from the sibling venice_web_search, but the sibling is never named, so an agent gets a clear purpose without explicit differentiation.

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 explains authentication options but gives no when-to-use guidance or alternatives, e.g. when to scrape a single URL versus calling venice_web_search. The agent must infer the selection criteria on its own.

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