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

The description discloses behavioral traits such as JavaScript rendering, anti-bot bypass, and proxy rotation, which complement the annotations (readOnlyHint, idempotentHint, openWorldHint). It adds value beyond annotations by detailing these capabilities, ensuring the agent understands the tool's scope and limitations.

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 concise (three sentences) and front-loaded with the tool's core function. Every sentence adds value: the first states the primary action and output formats, the second highlights key features, and the third emphasizes cost-effectiveness. No 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?

Given the tool's complexity (handles JS, anti-bot, proxy), the description covers essential aspects: output formats, key features, and pricing. With an output schema present, return value details are not needed. The description provides sufficient context for an agent to use the tool effectively.

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 100%, and the input schema already provides clear descriptions for all parameters (url, format, readability, wait_for). The description merely echoes output formats and mentions 'LLM-ready output' but does not add significant new meaning beyond 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 scrapes web pages and returns clean content in multiple formats (markdown, text, raw HTML). It highlights key capabilities like JavaScript rendering and anti-bot bypass, distinguishing it from sibling tools like scraping.spider.search (search) and other web scraping tools.

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 explicitly mentions handling JavaScript rendering and anti-bot bypass, indicating when this tool is appropriate. It implies usage for modern web pages requiring dynamic content extraction. However, it does not explicitly state when not to use it or list alternative tools for specific cases.

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