screenshot_page

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

With no annotations provided, the description carries full burden. It does not disclose whether the screenshot captures the full page or only the visible viewport, nor does it explain the behavior of the 'saveTo' parameter (e.g., whether it suppresses the base64 output). These are important behavioral traits for an AI agent.

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 sentence, which is concise but lacks important details about the scope of the screenshot and parameter behavior. It trades completeness for brevity.

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 optional parameter, no output schema), the description is minimally adequate but leaves ambiguity about the screenshot area and the side effects of 'saveTo'. A more complete description would clarify these 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?

The input schema has 100% coverage for its single parameter, which already explains the 'saveTo' option. The tool description adds no additional meaning beyond the schema's description, so it meets the baseline of 3.

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 'Capture page screenshot as base64 PNG' clearly states the action (capture) and resource (page screenshot) and output format (base64 PNG). However, it does not explicitly differentiate from sibling tool 'screenshot_by_uid', which might capture specific elements. A slight ambiguity remains whether it captures full page or just viewport.

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 like 'screenshot_by_uid', or any prerequisites such as page being fully loaded. The description lacks any usage context or exclusions.

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