puppeteer_screenshot

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

With no annotations, the description must carry the full burden of behavioral disclosure. It fails to mention what happens after the screenshot is taken—whether it saves to a file, returns a data URL, or requires further handling. Side effects, output format, and error behavior are entirely absent, leaving the agent uncertain about the tool's effects.

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 a single, front-loaded sentence that directly states the tool's purpose without redundancy. Every word earns its place, making it exceptionally concise and well-structured.

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 tool has no output schema and no annotations, so the description must compensate. It does not clarify what the tool returns (e.g., file path, base64 image) or how the captured screenshot is delivered. With four parameters, including optional sizing and element targeting, the tool is moderately complex, yet the description omits essential context for an agent to use it correctly.

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 input schema provides 100% coverage with descriptions for all four parameters (name, width, height, selector), so the baseline is 3. The description's phrase 'or a specific element' loosely maps to the selector parameter but adds no new meaning beyond what the schema already states.

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 tool's function: 'Take a screenshot of the current page or a specific element'. It uses a specific verb ('take') and resource ('current page or specific element'), and distinguishes itself from sibling tools like puppeteer_navigate by focusing on capture rather than navigation.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools like audit-seo or evaluate-page-structure are not mentioned, and there is no context about scenarios where a screenshot is preferred over other analysis tools. The description only states what it does, not when to apply it.

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