Web Page Screenshot

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating safe, repeatable reads. The description adds context about headless browser rendering and the Zyte provider, but does not disclose potential limitations like timeouts, JavaScript handling, or size 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?

The description is two concise sentences, front-loaded with the core action and output, followed by use cases and how it works. 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?

Given the tool's simplicity (one param), annotations, and existence of an output schema, the description covers the essential points. Missing details like URL restrictions or failure scenarios but not critical for this straightforward tool.

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?

Input schema has 100% coverage and the param description already states the output format. The tool description adds extra context: 'full-page' screenshot and 'headless browser renders', which go beyond the schema's 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 the action 'Capture a full-page screenshot of any URL' and the output format 'base64-encoded PNG image'. It lists use cases but does not differentiate from the sibling tool 'web.screenshot.capture', which could be confusing.

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 mentions use cases like 'visual verification, monitoring, or archiving', but provides no guidance on when to choose this tool over alternatives such as 'web.screenshot.capture'. There is no when-not-to-use or comparison.

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