alterlab_screenshot

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

Describes returning a full-page PNG screenshot via a real headless browser and working on anti-bot sites. No annotations provided, so description carries the burden; it covers key behavioral traits but could mention performance or cost.

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?

Four sentences, each providing essential information: purpose, anti-bot capability, output type, and parameter usage. No wasted words; front-loaded with main action.

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 no output schema, description adequately explains return value (full-page PNG in conversation). All parameters are described in schema and elaborated in text. Context is sufficient for agent usage.

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 coverage is 100%, so baseline is 3. Description adds usage context (e.g., 'Use wait_for to wait for a specific element') that goes beyond schema definitions, providing practical guidance.

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 clearly states the tool takes a screenshot of any website, captures a webpage as an image, or snapshots a URL visually. It distinguishes from siblings by mentioning anti-bot bypass capability and similarity to alterlab_scrape.

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?

Provides guidance on using wait_for and wait_until parameters. Implicitly distinguishes from alterlab_scrape for visual capture vs. data extraction, but lacks explicit when-not or alternatives.

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