screenshot

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

No annotations are provided, and the description does not explicitly state whether the operation is read-only or has side effects. While screenshots are typically non-destructive, this is not disclosed, leaving some ambiguity.

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 extremely concise, using a single sentence to convey the action and output options. No unnecessary words or repetition.

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 description covers the primary functionality and output, but does not mention potential edge cases (e.g., if both path and base64 return are desired, or what happens when saving to a path). This is minor for a simple tool, but a bit more detail could improve completeness.

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 path parameter is described in the schema ('File path to save image'), but the full_page parameter lacks any description beyond its default value. The tool description mentions 'saves to path' but does not clarify full_page behavior, leaving its semantics partially unexplained.

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') and specifies the output format (base64 string) or saving to a path. This is specific and distinct from sibling tools like navigation or DOM manipulation.

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 use for capturing visual page state, but does not explicitly state when to choose this over alternatives. However, its purpose is self-evident, and the mention of output options provides context.

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