screenshot

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only reveals the conditional output format, but omits details about side effects (e.g., scrolling, waiting), permissions (e.g., file system access), and whether the screenshot is of the viewport or full page.

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 short (one sentence) and front-loaded, but achieves conciseness at the expense of completeness. It omits critical information about parameters and usage context, making it insufficient for effective tool selection.

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 presence of sibling tools (e.g., 'screenshot_element'), the lack of annotations, and two parameters (including the undocumented 'full_page'), the description is incomplete. It fails to provide a comprehensive understanding of the tool's capabilities and limitations.

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 description coverage is 0%. The description adds meaning for the 'path' parameter (output format conditional), but completely ignores the 'full_page' parameter. This provides only partial compensation for the lack of schema descriptions.

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 ('Take a screenshot') and the conditional behavior based on 'path' parameter. However, it does not differentiate between full-page and viewport screenshots, nor does it distinguish from the sibling 'screenshot_element' tool, which captures a specific element.

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 provides minimal guidance on when to use this tool versus alternatives. It implies that omitting 'path' returns base64 data, while providing a path saves to a file, but does not specify when to prefer this over 'screenshot_element' or other strategies.

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