scrape_url

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context about modes and output types, but does not disclose other traits such as async behavior, return structure, or interactions between parameters like pdf boolean and output 'pdf'.

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 compact and front-loaded with the core purpose, followed by mode selection, output choices, and AI extraction guidance. Every sentence earns its place, and there is no filler or repetition of schema details.

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?

This is a 30-parameter tool with no output schema, yet the description is only three sentences. It covers the basics but omits important runtime context like return value shape, async mode, storage integration, and dependencies between flags such as pdf, screenshot, and output, which an agent may need to invoke advanced features correctly.

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 70%, so the schema carries most of the parameter documentation burden. The description adds useful meaning for the mode and output enums (e.g., 'browser (JS)' and 'auto (detect)') and explains the ai_enhance/ai_prompt relationship, but it does not compensate for undocumented or ambiguous parameters such as screenshot versus output screenshot.

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 states a specific verb and resource: 'Scrape a single URL.' The word 'single' distinguishes it from sibling tools like crawl_website and map_website, and the listed modes and output formats further clarify its scope.

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 gives clear context for using the tool on a single URL rather than crawling or mapping, and provides mode-selection guidance ('request (fast), browser (JS), auto (detect)'). It does not explicitly name alternatives or give when-not-to-use exclusions, but the single-vs-crawl distinction is clear enough.

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