web_scrape

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 explains that the tool fetches the URL content, strips HTML tags (scripts, styles, nav, etc.), converts to markdown, has a 5-second timeout, and requires a valid API key. This is sufficient transparency for a simple scrape tool.

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 and well-structured with a clear overview, process details, and limitations. It uses bullet points for the parameter list, minimizing cognitive load. Every sentence adds value without redundancy.

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?

The tool has only one parameter and a straightforward behavior. The description covers input, process, constraints, and output format (markdown). An output schema exists, so detailed return value explanations are not necessary. Minor gaps include no mention of error handling or rate limiting.

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 input schema provides only the parameter name and type with no description (0% coverage). The description adds meaningful information: 'url — The full URL to scrape (e.g. 'https://example.com/page').' This explains what constitutes a valid URL, adding value 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's purpose: 'Scrape a URL and return clean markdown text.' It specifies the verb (scrape) and resource (URL), and distinguishes itself from siblings like scrape_meta_tags and read_url by emphasizing the markdown conversion and paid-only restriction.

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 mentions that the tool is paid-only and requires an API key, and a 5-second timeout. However, it does not explicitly state when to use this tool versus other scraping or URL tools, nor does it provide exclusions or alternatives.

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