Screenshot a web page

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

Describes behavioral traits such as using a real browser, residential proxies, and stealth, which adds value beyond the schema. However, no annotations are provided and it does not disclose limitations, error handling, or rate limits.

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?

Two sentences, front-loaded information, no wasted words. Every sentence adds value.

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?

Covers the main purpose and output format (PNG) but lacks details on screenshot dimensions, error behavior, or prerequisites. With no output schema, more completeness would be beneficial.

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 only parameter 'url' is well-described in the schema. The description adds that the output is a PNG screenshot from a browser context, but does not add substantial new meaning beyond the schema. Baseline is 3 for 100% coverage.

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?

Clearly states it renders a URL in a real browser and returns a PNG screenshot. Includes specifics like residential proxies and stealth. However, does not explicitly differentiate from sibling tools (crawl, scrape) but the action is distinct.

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 clear context for use: 'to see a page visually or capture JS-rendered content.' Lacks explicit when-not or alternatives, but the context is sufficient for basic guidance.

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