chrome_screenshot

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

The description discloses basic behavior (capture screenshot) and return type, but lacks details on what exactly is captured (viewport vs full page), side effects, permissions required, or state dependencies (e.g., session must be open). No annotations are provided to compensate.

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 very concise: a single sentence for purpose, followed by structured Args and Returns sections. No unnecessary information is present, and the most important details are front-loaded.

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?

For a simple screenshot tool with an output schema (suggested by context), the description is adequate but not complete. It covers purpose and parameters but lacks behavioral details like what happens when output_path is empty, whether errors are specific, or how the screenshot is captured (e.g., viewport only).

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 description explains that 'session_id' is the session returned by chrome_open_session and 'output_path' is an optional file path for output PNG. This adds meaning beyond the schema, which only defines types and default values. Schema description coverage is 0%, so the description effectively compensates.

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 it captures a screenshot of the active page in a Chrome CDP session, distinguishing it from sibling tools like capture_active_screen. However, it does not explicitly differentiate from other Chrome-specific tools like chrome_navigate or chrome_click.

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 capture_active_screen or other screenshot tools. There is no mention of prerequisites or when to avoid using it.

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