Bright Data Web MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'cache lookup' and 'more reliable than scraping,' which adds useful context about performance and reliability. However, it doesn't cover other important behaviors like rate limits, authentication needs, error handling, or what 'structured data' specifically means in the return format.

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 extremely concise and well-structured: three short sentences that each add distinct value (purpose, parameter requirement, behavioral advantage). There's no wasted language, and key information is front-loaded.

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's moderate complexity (reading structured data from a specific website), no annotations, no output schema, and 0% schema description coverage, the description is minimally adequate. It covers the basic purpose and parameter but lacks details about return format, error cases, or how it differs from other web data tools. The mention of 'cache lookup' adds some helpful context.

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 meaningful context for the single parameter: 'Requires a valid zillow properties listing URL.' This clarifies that the 'url' parameter must be a Zillow properties listing URL, not just any URI. With 0% schema description coverage and only one parameter, this compensates adequately, though it doesn't specify URL format examples or validation details.

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's purpose: 'Quickly read structured zillow properties listing data.' It specifies the verb ('read'), resource ('zillow properties listing data'), and key characteristic ('structured'). However, it doesn't explicitly differentiate from sibling tools like 'scrape_as_html' or 'web_data_amazon_product' beyond mentioning 'more reliable than scraping'.

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 provides some usage context: 'Requires a valid zillow properties listing URL' and 'This can be a cache lookup, so it can be more reliable than scraping.' This implies when to use it (for Zillow property listings, preferring cache over scraping) but doesn't explicitly state when not to use it or name specific alternatives among the many sibling tools.

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