cdp_screenshot

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

With no annotations provided, the description must convey behavioral traits. It discloses that the output is 'image content' and that it captures the 'current page,' implying a read-only snapshot. However, it does not explicitly state that it does not modify the page, nor does it mention any side effects, session requirements, or limitations (e.g., only viewport by default). The description adds some value but could be more transparent.

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, clear sentence that immediately conveys the core function. It is front-loaded with the action and resource, and contains no filler or redundant information. Every word earns its place.

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 is simple, but the description lacks important contextual information. It does not explain the full_page parameter's effect, nor does it mention the need for a valid session_id (though the schema covers that). There is no output schema, but the description does state the return format ('image content'). Given the low complexity, the description is mostly sufficient but has clear gaps around parameters and session prerequisites.

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 50%: session_id is described in the schema, but full_page is not. The tool description does not mention either parameter, so it adds no meaning beyond the schema. Full_page's behavior (full-page vs. viewport-only capture) is left unexplained, and the description does not clarify how the parameters relate to the tool's function.

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: 'Capture the current page as a PNG screenshot (returned as image content).' This uses a specific verb ('capture'), identifies the resource ('current page'), and specifies the output format ('PNG screenshot'). It is distinct from sibling tools like cdp_navigate or cdp_click, which perform different actions.

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 does not provide any guidance on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., an active session from cdp_connect), conditions for use, or situations where another tool (such as cdp_content for DOM text) would be more appropriate. The usage context is only implied by the tool's name and basic function.

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