alterlab_screenshot

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

The description mentions output format (PNG) and rendering method (headless browser), but lacks details on error handling, authentication, rate limits, or behavior on invalid URLs. No annotations exist to supplement.

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 four concise sentences, each adding distinct information: main action, output format, rendering method, and a usage tip. No unnecessary 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?

The description covers basic usage and output but lacks context about error handling, timeouts, or comparisons to sibling tools. It leaves the agent to infer some aspects.

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%, baseline 3. The description adds context for wait_for by explaining its purpose ('to wait for a specific element'), improving over the schema description.

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 'Take a full-page screenshot of a URL', specifying the verb and resource. It implicitly distinguishes from sibling tools like alterlab_scrape or alterlab_extract by focusing on visual capture. However, it does not explicitly differentiate from siblings.

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 a usage tip for the wait_for parameter but does not offer guidance on when to use this tool versus alternatives, nor does it mention when not to use it.

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