screenshot_web

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

The description discloses the primary behavior (capturing screenshots, returning presigned URLs) and mentions features like AI targeting and PDF export. However, it does not mention constraints like private IP blocking (present in schema) or potential rate limits. With no annotations, the description provides moderate but incomplete transparency.

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 two sentences: first states the main purpose, second lists key features. It is concise, front-loaded, and contains no extraneous 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?

Given the tool's complexity (8 parameters, no output schema), the description covers the essential use cases and return type. It omits details like default viewport (in schema) and job retrieval (in schema), but overall provides enough context for an agent to understand the tool's capabilities.

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. The description reinforces parameter meanings (e.g., 'AI-targeted sections' for 'description', 'full-page' for 'fullPage') but adds little new semantic value beyond what the schema already provides.

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 verb 'Capture' and the resource 'screenshot of any public website URL', and lists distinct features (AI-targeted sections, full-page, PDF, custom viewport) that differentiate it from sibling tools like screenshot_mobile and render_html.

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 implies usage for public websites but does not explicitly state when to use this tool over alternatives or provide exclusions. It lacks guidance on when not to use it (e.g., for private/internal sites or when a mobile-specific viewport is needed).

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