web_unblocker

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 adds that requests go through a proxy network and that JavaScript rendering is optional, but it does not disclose response formats, error behavior, rate limits, authentication, or how to enable the optional rendering. This is some behavioral context but not comprehensive.

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 paragraphs plus a one-item bullet list. It front-loads the main purpose and includes a usage directive. The 'request: Request' line is slightly tautological but the structure is economical.

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 general-purpose tool with no output schema and no annotations, the description provides essential purpose and usage guidance but leaves operational gaps: no response format, no error handling, no rate limit info, and no way to activate the advertised JS rendering. It is minimally viable but incomplete.

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 only provides generic placeholders for 'args' and 'operation'. The description adds concrete meaning: it names the only operation 'request' and specifies its required parameter 'url' (e.g., 'request (required: url)'). This goes beyond the schema. However, it does not document how to enable the mentioned optional JavaScript rendering, so coverage is incomplete.

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?

Description opens with a clear verb ('Fetch'), resource ('raw HTML/content of any URL'), and mechanism ('through OWN's anti-bot proxy network'). It explicitly frames itself as a general-purpose fallback, distinguishing from dedicated sibling tools like realtime_amazon_data and realtime_zillow_data.

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?

It explicitly states 'Use only when no dedicated API covers the target site' and advises 'Prefer the structured tools (Amazon, Zillow, etc.) when one exists.' This provides clear exclusionary criteria and names alternatives.

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