scrape_url

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

With no annotations, the description bears full responsibility. It discloses required environment variables, the bypass behavior, return format, and authorization. However, it omits details on rate limits, error handling, or timeouts, which would be helpful for agents.

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 three well-structured sentences: action and capability, return format and prerequisites, and legal constraints. No wasted words; front-loaded with the core function.

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 has 2 parameters, no output schema, and no annotations, the description covers the essential aspects: what it does, prerequisites, return format, and authorization. It lacks error handling details but is otherwise complete for a simple fetch 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 50% (only json_output has a description). The description adds context for the URL parameter (public URL) and for json_output (structured JSON), but does not specify URL format or validation rules. Baseline for 50% coverage is 3, and the description adds marginal value.

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 explicitly states the tool fetches any public URL through Bright Data's Web Unlocker API, bypassing protections and returning Markdown. This clearly distinguishes it from sibling tools, which are all search-oriented (e.g., search_domain, search_ip).

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 the tool is for fetching public URLs that are protected, and includes authorization requirements. It does not explicitly state when not to use it or compare it to siblings, but the sibling tools are all search functions, making the use case clear.

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